Skip to content
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.

Latest commit

 

History

History
24 lines (13 loc) · 1.61 KB

t-testing-acquisition.md

File metadata and controls

24 lines (13 loc) · 1.61 KB

Testing legacy acquisition

The following information helps you roundtrip an legacy acquisition campaign link that is based on a device fingerprint.

If the mobile app is not yet in Google Play, you can select any mobile app as a destination when creating the campaign link. This only affects which app the acquisition server redirects you to, after you click the acquisition link, not the ability to test the acquisition link.

  1. Navigate to Use Legacy Acquisition Links in Adobe Mobile Services and generate an acquisition campaign URL.

    For more information, see Use Legacy Acquisition Links.

  2. From the mobile device on which you will install the app, click the generated link.

    Adobe's servers (c00.adobe.com) store the fingerprint and then redirect to the App Store. The app does not have to be downloaded for testing.

  3. On the same mobile device that you used in step 2, launch the application for the first time.

    The easiest way to ensure that this happens is to delete and install the app again.

Remember the following information:

  • The acquisition server provides an attribution match that is based on IP address and user-agent information that recorded in the link click (step 2) and when the app is launched (step 3).
  • By using HTTP monitoring tools, hits that are sent from the app can be monitored to provide verification of the acquisition attribution.

Tip: Variations in the user-agent sent might cause attribution to fail.