Support Home > Campaign Management > Create a Twitter Reengagement Campaign

Create a Twitter Reengagement Campaign

Twitter is a SAN (Self-Attributing Network) but is still eligible to claim events as re-engagement conversions. The following document defines the process for creating a Twitter reengagment campaign within Free App Analytics.

NOTE: Before the Twitter reengagement campaign can be setup within Free App Analytics, ensure that a Twitter Ads account has been created, target events within Twitter have been created and at least one Twitter Ads account has been authenticated within Free App Analytics. For more information on authenticating with Twitter, refer to our Create a Twitter Campaign support documentation.

NOTE: The reengagement campaign set up in Free App Analytics sends event data to Twitter in order to build audiences and/or retarget known users and to know when those efforts are successful. If no corresponding reengagement campaigns are setup within Twitter, Free App Analytics will only send event data to Twitter for audience construction and targeting, but will not “convert” based on reengagement campaigns.

Create a Free App Analytics Tracker

  1. Log in to Free App Analytics.
  2. Select the desired Account and App.
  3. If not already created, create a new Twitter campaign. For more information about creating campaigns, refer to our Create an Install Campaign support documentation.

    BEST PRACTICES: In order to help with campaign organization, it is recommended that a segment be created for reengagement.


  5. Enter a Tracker Name.
  6. Select Segment Tools () > Add a Tracker.
  7. Select Tracker Type > Reengagement.
  8. Select a Network > Twitter:
    1. Twitter — iOS
    2. Twitter — Android
  9. Select the Twitter Account to associate with this tracker.
  10. NOTE: Multiple Twitter accounts may be selected.

  11. Enter the app Apple ID (iOS) or Bundle ID (Android). For further information about locating the Bundle ID, click here.
  12. NOTE: In the Free App Analytics UI (User Interface) the terms “Package Name” and “Bundle ID” are both used to represent the app ID. The same ID number should be used for both fields.

  13. Select the Target Event.
  14. NOTE: The Twitter Target Event should match the event that will be tracked through Free App Analytics. If there is not an exact match for the events listed in the Event Matching section, choose the closest match to maintain a handle on changes to event naming convention between Twitter/Free App Analytics.

  15. Select the Post-Engagement Attribution Window.
  16. NOTE: By default, the Post-Engagement Attribution Window is set to 14 days.

  17. Select the Post-View Attribution Window.
  18. NOTE: By default, the Post-View Attribution Window is set to 0 days. The Attribution Window setting selected here is reccomended to match the attribution window that is within Twitter. If the attribution windows do not match, there will be discrepancies in the data reported.

  19. Select the Event Matching Event.
  20. NOTE: Reengagement attribution will be assigned for the created tracker in response to the event that is selected within in the Event Matching drop-down.

  21. Click Submit. (If no further trackers need to be created).
  22. Click Save and Add Another Tracker. (If additional trackers need to be created).
  23. Click Save & Create Postback. (To navigate directly to the Partner Configuration page).


A. Campaign and Segment selection/creation section.
B. Select the Twitter Account(s)

Create a New Free App Analytics Postback Configuration

  1. Select Apps & Assets > Partner Configuration.


  3. Click Add a Configuration.
  4. Select Network Configuration > Twitter:
    1. Twitter—iOS
    2. Twitter—Android



  5. Locate the desired postback event and Select Edit Postback.
  6. Enter the App ID:
    1. iTunes App ID (iOS)
    2. Package Name (Android)
  7. Enter the Twitter Conversion Type.
  8. NOTE: The Twitter Conversion Type must match the conventions established by Twitter. For a list of Twitter events, click here.

  9. Select a Delivery Delay.
  10. NOTE: By default, the Delivery Delay is set to Realtime Delivery.

  11. Select the number of Retry Attempts.
  12. NOTE: By default, the number of Retry Attempts is set to 3 Attempts.

  13. Select the Delivery Method.
  14. NOTE: By default, the Delivery Method is set to All.

  15. Click Save.



Last Modified: Feb 17, 2020 at 5:23 pm