Testing Version 3 Acquisition
Instructions to help you roundtrip a V3 acquisition campaign link based on a device fingerprint.
Important: V3 Acquisition refers to the acquisition links you create with the Acquisition Builder in the Adobe Mobile Services UI. You must upgrade to iOS SDK version 4.6.0 or newer to use this feature.
If the mobile app is not yet in the App Store, you can choose any mobile app as a destination when creating the campaign link. This affects only which app the acquisition server redirects you to after clicking the acquisition link, but not the ability to test the acquisition link.
- Perform the prerequisite tasks in Mobile App Acquisition.
- Navigate to the Acquisition Builder in the Adobe Mobile Services UI and generate an acquisition campaign URL.
For more information, see Use Acquisition Builder in the Adobe Mobile Services documentation.
If you refer to both iOS and Android apps in the acquisition link, use the Apple Store as the default store.
- Open the generated link in a desktop browser, then open http://c00.adobe.com/v3/<appid>/end.
You should see the contextData in the JSON response:
If you don't see contextData, or some of it is missing, ensure that the acquisition URL follows the format specified in Create Acquisition Link Manually in the Adobe Mobile Services documentation.
- Verify that the following settings in your config file are correct:
The server should be c00.adobe.com
appid should equal the <appid> in your acquisition link
referrerTimeout should have a value greater than 0
- (Conditional) If the ssl setting in your app's config file is true, update your acquisition link to use the HTTPS protocol.
- Click the generated link from the mobile device on which you will install the app.
Adobe's servers (c00.adobe.com) store the fingerprint and then redirect to the App Store. The app does not need to be downloaded for testing purposes.
- Launch the application for the first time from the same mobile device used in Step 6.
You can delete and then re-install the app, if necessary.
- (Optional) You can enable debug logging of the SDK to obtain additional information.
If everything works correctly, you should see following logs:
"Analytics - Trying to fetch referrer data from <acquisition end url>" "Analytics - Received Referrer Data(<Json Object>)"
If you don't see the above logs, ensure that you have performed Steps 4 and 5.
The following table contains information to explain possible errors:
|"Analytics - Unable to retrieve acquisition service response ()"||A network error occurred.|
|"Analytics - Unable to parse acquisition service response ()"||The response is not in the correct format.|
|"Analytics - Unable to parse acquisition service response (no contextData parameter in response)"||There in no contextData parameter in the response.|
|"Analytics - Acquisition referrer data was not complete, ignoring"||a.referrer.campaign.name is not included in contextData.|
|"Analytics - Acquisition referrer timed out"||Failed to get the response in the time defined by referrerTimeout. Increase the value and try again. You should also ensure that you've opened the acquisition link before installing the app and that you're using the same network when you click the URL and open the app.|
Failed to get the response in the time defined byreferrerTimeout. Increase the value and try again.
You should also ensure that you've opened the acquisition link before installing the app and that you're using the same network when you click the URL and open the app.
The acquisition server provides an attribution match based on the IP address and user-agent information recorded in the link click (Step 6) and when the app is launched (Step 7). You should be on the same network when you click the URL and when you open the app.
Hits sent from the app can be monitored (using HTTP monitoring tools) to provide verification of the acquisition attribution. You should see one /v3/<appid>/start request and one /v3/<appid>/end request sent to the acquisition server.
Variations in the user-agent sent might cause attribution to fail. Ensure that http://c00.adobe.com/v3/<appid>/start and http://c00.adobe.com/v3/<appid>/end have the same user-agent values.
The acquisition link and the hit from the SDK should be using the same HTTP/HTTPS protocol. If they’re using different protocols (for example, the link uses HTTP and the SDK uses HTTPS) the IP address might differ for each request (on some carriers). This could cause the attribution to fail.
Parent topic: Acquisition