Google

Step 1: Generate link_id on Google

1) Go to "Tools" in Google Ads, and find "Data Manager --> Third-party app analytics".

2) Click "+" icon.

3) Select Tenjin in the "App analytics provider" list, and select your mobile app's platform. If Tenjin is not found, select Other provider, and enter: 8670853329.

4) Select the relevant app under "Look up your app" and click "Create Link ID".

5) Copy the newly created Link ID, which can identify your app in Google Ads.

6) You need to repeat the above steps when creating exclusive Link IDs for different apps.

   Note:

   If you work with one or more agency partners, we recommend that you be the owner of the link IDs for all of your apps. This allows you to manage link IDs conveniently, such as sharing the link ID with other accounts if needed, or removing links from other accounts anytime.

   Even if you don't manage your account, we recommend that you create link IDs in an admin account, and then share the link ID with any other accounts that need the link ID for conversion tracking or re-marketing.

How to authorize Link ID to agents (if you have any):

1. Click "Tools" and "Data Manager" in Google Ads. Find the Link ID and "Share with another account".

2. Enter the Customer ID of the agency's Google Ads account.

3. Click "Next" >> "Send Invitation". You can see that the Link ID sharing invitation has been sent to the agent. When the agent accepts the invitation, the status will change to Shared.

More details on sharing Google Ads Link ID, please visit https://support.google.com/google-ads/answer/7365001

Step 2: Enable Postback on SolarEngine

1) Access Path:  Attribution --> Integrated Partner --> Google Ads --> Partner Configuration

2) Enable postback and enter the Link ID.

3) It is recommended to keep the attribution window as 30 days, same with Google Ads.

        By default, only installs are sent to Google. If you want to postback other in-app events, please enable "event postback". The following is an example. Please set based on your needs.

Step 3: Import Events to Google*

1) Return to Google Ads Overview page, click "Create", and select "Conversion action".

2) Click + New conversion action.

3) Select App in the conversion type list, then select "Third-party app analytics" and click "Continue".

4) Check "first_open" as the event to import, click "Import and Continue", and then click "Done". This event must be imported, otherwise we cannot attribute installs to Google .

5) After entering the Conversions > Summary page, you can see the third-party conversion events. If the event does not appear in the list or has been removed from the Google Ads conversion import list, click "View all conversion actions" and you will see the Status filter.

6) When you create campaigns, please select "App promotion" as your goal, and select the events you want to optimize when bidding.

Step 4: Associate Google Account

To pull ad spending from Google and calculate ROAS, please connect Google account with SolarEngine.

Guide:  https://help.solar-engine.com/en/docs/Google-AdWords

If you promote iOS apps on Google Ads,

1. Please enable ODMInfo Attribution when integrating SDK, and provide your SolarEngine AM with bundle_id and storeid, so we can note Google to add your app package on whitelist. Currently, Google only allows apps on the whitelist to access ODMInfo values, which are largely helpful to increase iOS attribution accuracy.

2. If ODMInfo attribution is not enabled, Google will not share iOS install attributions to any MMP arising from:

• YouTube channels/advertising campaigns
• Google Search Ads

Attributed installs from other channels are available, but only when SolarEngine can access IDFA. For scenarios where iOS attributed installs cannot be sent, although you can still view these attributions in your Google Ads account, you won't be able to see them in SolarEngine because Google does not share the data with us. You can try our Google Web to App  as a solution.

   There are some report metrics being named differently on Google and SolarEngine. Here is a comparison table:

   You may find that there is a gap between Google's and SolarEngine's attribution results. This data difference is caused by the following reasons: