If you use a Localytics ad tracking
partner to monitor marketing conversion, you can track your app install campaigns in the Localytics
Attribution
Dashboard.
Ensure that you've enabled Third-party
Attribution and that you've pasted your Attribution ID into your ad tracking partner's
dashboard application.
Then, set up and execute your user acquisition campaigns in your ad tracking partner's system.
Your ad tracking partner will postback acquired users to Localytics using the Localytics
Attribution API.
The
Localytics
Attribution API enables your ad tracking partner
to send "attribution requests" to
Localytics. At
a high level, an attribution request consists of
- a device or advertising identifier for a new end user
- details about how you acquired that new end user
The details must include the acquisition source, but can also include the acquisition
campaign name, ad group name, and creative name. If the campaign name is not provided,
Localytics will create a campaign of the form "[Ad
tracking partner name] campaign," so that your user acquisition data can be tracked in the
Attribution
Dashboard. If sent by your third-party
attribution partner, ad group name and creative name are available in your log exports in S3.
Note: When you enable Third-party
Attribution in
Attribution Settings,
Localytics will
delay processing your app's events for 10 minutes to provide your ad tracking partner with
sufficient time to complete app install postbacks after your app acquires new users. This is
typically not a concern for production applications, but you may prefer to disable this setting
for your testing/development applications, because the feedback loop between sending an app
event to
Localytics and the event's
incorporation into the
Localytics
Dashboard will be slightly longer than
usual.