After an event type (formerly action tracker) that uses a tracking pixel has been set up for you by Impact, you can begin working on integrating it into your website. This test is required to validate the event type and ensure it is properly integrated.
Perform this test after you have finished integrating Impact's pixel tracker according to your technical integration plan. You should receive this document during your Impact onboarding sessions.
Note
Before testing the event type, start a fresh browser session and disable all ad-blocking browser extensions and add-ons.
From the left navigation bar, select
[Menu] → Settings.On the right, under Tracking, select Event Types.
On the right, under Actions, select
[Drop-down menu]→ Test.Optionally, change the Landing Page URL. All event type tests will use your program's default landing page unless otherwise specified.
Select Start Test in New Window.
Complete a test conversion on your website. See the Test details section below to learn more about what to do once you select Start Test in New Window.
Note
The test conversion must happen within 5 minutes of you selecting Start Test in New Window or the test session will time out and you will need to start again. Impact recommends having exactly what items (and their quantities) written down next to you when you begin your test.
Once you select Start Test in New Window, a new browser tab will open. This new tab will immediately direct to the URL indicated in Step 4 above.
Selecting Start Test in New Window emulates partner-driven traffic clicking on a partner-hosted ad. Because of this, you must complete the test conversion on the same browser, and in the same session, as the one you used to select Start Test in New Window.
If you are testing an Online Sale event type and your shopping cart allows for multiple items to be listed in cart, a best practice is to purchase at least 2 different items with more than 1 quantity each, but not the same quantity across multiple items. If possible, include a promo code.
Note
You should perform multiple tests using different items, item quantities, and (if applicable) promo codes. However, your event type will be validated after its 1st successful test.
Less than a minute after you generate the conversion data (i.e., convert on your website), impact.com will process the conversion data and determine whether the data was submitted successfully or not. Do not close the tab on which you selected Start Test in New Window—this screen will show you the results of your test.
If you generate conversion data and the screen continues to show "Please generate a conversion on your site," an error exists within your pixel implementation. you will need to consult with your development team.
Your test results screen (the Verify Information section) will show you 3 sets of data.
All required tracking values that were not received correctly by Impact. These will be flagged.
Required tracking values that failed to register. These will require you to double-check your tracking code integration to determine why the required values were not passed to Impact.
Required tracking values that were passed successfully to Impact. These will need to be verified, which is done by selecting the relevant checkbox.
Note
Item price amounts are expected to be pre-tax and post-discount amounts. When all tracking values are successfully passed and all validation checkboxes are checked, select Test Passed. Congratulations! Your event type is validated and successfully integrated.
If you have a staging environment you want to test the event type in before testing it in your production environment, you must add your staging environment's domain and path to your site Definitions, which you can do by following these steps:
From the left navigation bar, select
[Menu] → Settings.On the right, under Tracking, select General.
Next to Site Definition select
[Edit].Add your staging environment's domain and path. Do not include the protocol or any query string.
For example:
impact.com/partnershipcloud/optimize
Select Save.
The process is the same for testing in a staging environment as it is for testing in a production environment.