Verify that the following settings in your config file are correct:
The server should be
should equal the
in your acquisition link.
should have a value greater than 0.
(Conditional) If the SSL setting in your app's config file is
, update your acquisition link to use the HTTP protocol instead of HTTPS.
Click the generated link from the mobile device on which you want to install the app.
Adobe's servers (
) store the fingerprint and redirect to the App Store. The app does not need to be downloaded for testing.
Launch the application for the first time from the same mobile device that you used in step 6.
You can delete and install the app again, if necessary.
(Optional) 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 do not see these logs, verify that you completed steps 4 and 5.
Here is some information about possible errors:
Analytics - Unable to retrieve acquisition service response (<error message>)
A network error occurred.
Analytics - Unable to parse acquisition service response (<error message>)
The response is not in the correct format.
Analytics - Unable to parse acquisition service response (no contextData parameter in response)
There is no
parameter in the response.
Analytics - Acquisition referrer data was not complete, ignoring
is not included in
Analytics - Acquisition referrer timed out
Failed to get the response in the time that is defined by
. Increase the value and try again. You should also ensure that you opened the acquisition link before installing the app and that you are using the same network when you click the URL and open the app.
Remember the following information:
The acquisition server provides an attribution match that based on the IP address and user-agent information that was 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.
By using HTTP monitoring tools, hits that are sent from the app can be monitored to provide verification of the acquisition attribution.
You should see one
request and one
request that are sent to the acquisition server.
Variations in the user-agent sent might cause attribution to fail.
have the same user-agent values.
The acquisition link and the hit from the SDK should be using the same HTTP/HTTPS protocol.
If the link and the hit are using different protocols, where for example, the link uses HTTP and the SDK uses HTTPS, the IP address might differ on some carriers for each request. This could cause the attribution to fail.
The Marketing Links are cached on the server side with a ten-minutes expiration time.
When you make changes to Marketing Links, you should wait about 10 minutes before using the links.