Français Italiano Português do Brasil

Testing Reconnect Campaigns

Follow

To test your Reconnect campaigns, do the following:

  1. Pick a test user that's on your ESP’s mailing list and then navigate to your website.
  2. Trigger or manually fire an identification event  in the console.
  3. Upload a subscriber list that includes your test user’s identifier using the Sync button for your integration, in the Reconnect Integrations tab.
  4. Select an audience that includes your test user OR create a dedicated test audience. Make sure the conditions you set for your test audience are unique, so that no "regular" users will accidently be allocated to this audience.
  5. Trigger the relevant event on the website OR change a feed attribute value to meet the email's trigger criteria (you can find the criteria in the Reconnect trigger settings).  Note: Take special care to avoid meeting any of the Cancel Send criteria. 
    • Test the event in a staging environment to ensure it works as expected.
    • If you are triggering an event from your website or app, make sure the event is properly implemented
  6. Wait for the delay period to pass before checking the test user's inbox for the Reconnect email.
    • If you find the expected email in the test user's inbox, your Reconnect flow is working properly!
    • If the expected email isn't in the test user's inbox, check the ESP log.
    • If the payload is in the ESP log but it wasn't sent to the test user, this means that the Dynamic Yield portion of the flow is working properly. Work with your ESP to identify any delays or restrictions in processing triggered campaigns.

Testing specific campaign types

In addition to these general steps, some campaign types require additional steps for testing:

Price Drop:

  1. Fire an Add to Cart event with a product that matches the campaign's trigger conditions (if your campaign is set to be triggered only for items from the “shoes” category, make sure the product you add to your cart is from that category).
  2. After the event fires, change the price of the product you're testing in your product feed and then sync the feed (by file or API). Make sure to decrease the price of the product by the amount/percentage you defined in the campaign’s trigger settings (if your campaign is set to be triggered when a product price drops by at least 10%, and the test product's price is $100, decrease the price by at least $10).
  3. Wait for the campaign's scheduled time.
    Important: When you do the test, make sure to set the Schedule to a time close to when you finalize these steps, to minimize your wait time.

Change in User Attribute:

  1. Upload a User Data feed. Make sure that:
    • The identifier you use in the feed matches the type you set in the Reconnect ESP integration.
    • The feed syncs successfully.
      Note: Change in User Attribute campaigns are triggered by a change in a feed value and NOT by an event, so step 5 (trigger an event) in the previous procedure isn't relevant here, whereas a successful feed sync is. 
  2. Change an attribute value in the relevant User Data feed, according to your campaign’s trigger setting, and sync the feed again.