Set Up NVECTA as Your Mobile Measurement Partner (MMP) for Google Ads and Meta

Modified on Fri, 13 Nov at 4:24 AM

Quick summary

This article explains how to set up NVECTA as the mobile measurement partner (MMP) for your Google Ads and Meta app campaigns. The setup is the same for both ad networks except for one step: getting the ID that connects your ad account to NVECTA. You get a Link ID from Google Ads or an App ID from a Meta app, share it with the NVECTA support team, and then analyze the installs and in-app events your campaigns bring in, right inside NVECTA Insights.

Why app campaigns need a Link ID or App ID

For web campaigns, you add tracking macros to your ad URLs so NVECTA knows which campaign sent each visitor. App campaigns work differently: the ad takes users straight to Google Play or the App Store, so there is no landing page URL to carry those macros.

An ID from the ad network does that job for mobile. It connects your ad account with NVECTA, so installs and in-app events in your app can be attributed to the campaign that drove them:

  • Google Ads: a Link ID that you create in Google Ads Data manager.
  • Meta: the App ID of a Meta app that you create in Meta for Developers.

How the setup works

StepWhat happensWho does it
1Get your ID: create a Link ID in Google Ads, or create a Meta app and copy its App IDYou
2Share the ID with NVECTA supportYou
3Add the ID to your NVECTA account from the backendNVECTA support team
4Analyze attributed installs and in-app events in InsightsYou

Google Ads and Meta at a glance

DetailGoogle AdsMeta
ID you shareLink IDApp ID of a Meta app
Where you create itGoogle Ads > Tools > Data managerMeta for Developers > My Apps > Create App
Access you needAdmin access to the Google Ads accountA Meta for Developers account, plus admin access to the business portfolio that owns your Meta ad account
How many IDsOne Link ID per app and platformOne App ID for your Meta app, covering Android and iOS
Ad Source value in InsightsGoogleMeta

Before you begin

› For both ad networks:

› For Google Ads:

  • Admin access in Google Ads: you have admin access to the Google Ads account that runs your app campaigns. Only an admin can create a Link ID.

› For Meta:

  • Meta for Developers account: you can log in to Meta for Developers with the same Facebook account you use for Meta ads, or one that has access to your Meta ad account. The first time you open it, Meta asks you to create a Meta for Developers account in four short steps: Register, Verify account, Contact info and About you.
  • Admin access to your business portfolio: you are an admin of the business portfolio (Business Manager) that owns your Meta ad account.
  • Ad account ID: the ID of the Meta ad account that runs your app install campaigns.
  • App store details: your Android package name, and your iOS bundle ID and App Store ID.
  • Privacy details and app icon: a public privacy policy URL, a data deletion URL or instructions, and a 1024 × 1024 app icon.

Step 1: Get your ID from Google Ads or Meta

This is the only part of the setup that's different for each ad network. Follow the section for the network you advertise on, or both sections if you run app campaigns on Google Ads and Meta.

For Google Ads: create a Link ID

Where: Google Ads > Tools > Data manager > + Connect product > Third-party app analytics

  1. Sign in to your Google Ads account.
  2. Click Tools, then click Data manager.
  3. Under Connected products, click + Connect product.

  1. In Choose a data source, search for Third-party app analytics, select it and click Continue.

  1. On the Link third-party app analytics to Google Ads screen, click Create link ID. If your account already has a third-party app analytics link, click the + button to add another one.

  1. In the Create a new link to your provider window, open the App analytics provider dropdown and select Kochava.
  2. Under Select your mobile app's platform, choose Android or iOS.
  3. In Look up your app, enter your app name, package name or publisher, and select your app from the results.

  1. Click Create link ID.
  2. Copy the Link ID with the copy button, then click Done. Keep the Link ID handy for Step 2.

› Keep these points in mind:

  • One Link ID per app and platform: a Link ID covers one app on one platform. If your app is on both Android and iOS, create a Link ID for each platform and share both.
  • Unverified status is expected: right after you create it, Google Ads shows the link as Unverified. The status changes once the Link ID is added on the NVECTA side and data starts reaching Google Ads.
  • Don't regenerate the Link ID: regenerating it stops the old Link ID from working. If you do regenerate it, share the new Link ID with NVECTA support right away.

For Meta: create a Meta app and copy its App ID

Where: Meta for Developers > My Apps > Create App, then App settings > Basic and App settings > Advanced

The App ID only works for tracking when the Meta app is connected to your business portfolio, has no app restrictions and is set to Live. Follow the seven parts below in order.

› Part 1: Create the app

  1. Go to Meta for Developers and log in with the Facebook account that has access to your Meta ad account.
  2. On the Apps page, click Create App. If Meta shows a There's a new way to create apps with Meta message, click Create app to continue.

  1. On App details, enter an App name, for example NVECTA Tracking, check the App contact email, and click Next.

  1. On Add use cases, select Create & manage app ads with Meta Ads Manager and click Next. It is listed near the top under Featured. If it is greyed out, clear any other use case you selected first.

  1. On Which business portfolio do you want to connect to this app?, select the business portfolio that owns your Meta ad account and click Next. Don't choose I don’t want to connect a business portfolio yet.

  1. On Publishing requirements, click Next.
  2. On Overview, check the app name, use case and business portfolio, then click Create app.
  3. If Meta asks you to re-enter your Facebook password, enter it and click Submit. Meta then opens your app's dashboard.

Note

Choose the use case carefully, because Meta doesn't let you remove a use case after the app is created. If Create & manage app ads with Meta Ads Manager isn't listed, select Others under Filter by, select Other and choose Business as the app type instead. That also works for NVECTA.

› Part 2: Fill in the basic settings and add your platforms

Where: App settings > Basic

  1. In the left menu of your app's dashboard, click App settings, then click Basic.
  2. Fill in Privacy policy URL, User data deletion, App icon and Category. Meta needs these before the app can go live.
  3. Check that Business portfolio shows the business portfolio that owns your Meta ad account.
  4. Click Add platform, select Android, iOS or both, and click Next.

  1. For Android, select Google Play Store in Select Android Store and click Next. Enter your app's package name in Package Names and its main activity in Class name. Key hashes can stay empty if your app doesn't use the Facebook SDK.

  1. For iOS, enter your app's Bundle ID, and its App Store ID in iPhone Store ID.

  1. Click Save Changes.

› Part 3: Remove app restrictions and authorize your ad account

Where: App settings > Advanced

  1. Click App settings, then click Advanced.
  2. Under App restrictions, leave Age restriction set to Anyone (13+) and keep References alcohol, GDPR Restricted and Country restricted turned off. Any restriction stops measurement partners such as NVECTA from reading the app.
  3. Under Advertising accounts, add the ID of the ad account that runs your app install campaigns to Authorized ad account IDs.
  4. Click Save Changes.

› Part 4: Switch the app to Live

  1. At the top of the dashboard, next to App Mode: Development, switch the toggle to Live.
  2. If Meta doesn't let you switch, it lists the missing fields. These are usually the ones from Part 2, step 2. Fill them in and switch again.

Note

An app in Development mode can't be used for install tracking, so make sure App Mode shows Live before you share the App ID.

› Part 5: Accept the Advanced Mobile Measurement Terms

To let NVECTA measure your Meta app installs, accept Meta's Advanced Mobile Measurement Terms.

  1. Open the Advanced Mobile Measurement Terms page in Meta for Developers.
  2. Under Advanced Mobile Measurement, select the app you created from the dropdown.

  1. Scroll to the bottom of the terms and click Accept.

Apps listed under The following apps have not accepted the terms at the bottom of the page still need to accept them.

› Part 6: Copy the App ID

  1. Click App settings, then click Basic.
  2. Copy the value in the App ID field. The same App ID also appears at the top of the dashboard. Keep it handy for Step 2.

› Part 7: Test the App ID

  1. In your browser, open https://graph.facebook.com/ followed by your App ID, for example https://graph.facebook.com/1234567890123456.
  2. Check the response. When the App ID is ready for tracking, Meta shows your app's details, including its name and id:
JSON
{
  "category": "Business",
  "link": "https://www.facebook.com/games/?app_id=1234567890123456",
  "name": "NVECTA Tracking",
  "id": "1234567890123456"
}
  1. If Meta shows an error instead, the App ID isn't ready yet. An app that is still in Development mode returns an error like this one:
JSON
{
  "error": {
    "message": "Unsupported get request. Object with ID '1234567890123456' does not exist, cannot be loaded due to missing permissions, or does not support this operation. ...",
    "type": "GraphMethodException",
    "code": 100,
    "error_subcode": 33
  }
}

Fix the cause, then open the link again. Check that the app shows Live (Part 4) and has no app restrictions (Part 3). If the error says An access token is required to request this resource, the ID isn't a valid App ID, so copy it again from App settings > Basic (Part 6).

› Keep these points in mind:

  • Share only the App ID: never share the App secret shown next to it, and don't share a Page, Pixel, ad account or business portfolio ID instead.
  • One App ID for both platforms: Android and iOS are added to the same Meta app, so you share one App ID for both.
  • Check before you share: the app shows Live, App settings > Advanced has no app restrictions, and your ad account is listed under Advertising accounts, the Advanced Mobile Measurement Terms are accepted (Part 5), and the Graph API link in Part 7 shows your app's details.

Step 2: Share your ID with NVECTA support

Send your ID to the NVECTA support team by raising a support ticket. In your ticket, include:

  • Your app name
  • The platform: Android, iOS or both
  • The ad network: Google Ads, Meta or both
  • The ID: the Link ID for each platform (Google Ads) and the App ID (Meta)

The support team adds the ID to your NVECTA account from the backend, which creates the connection between your ad account and NVECTA. You don't need to change anything in your app.

Step 3: Analyze app installs in Insights

Where: Analytics > Insights > + Create New Report > Insights

Once the connection is live, installs and in-app events that come from your Google Ads and Meta campaigns carry their attribution in NVECTA. Attribution needs live ad traffic, so make sure your app campaigns are running. For Meta, wait two to three days after the integration goes live before you check. Then build an Insights report to see installs by source and campaign.

  1. Click Analytics, then click Insights.
  2. Click + Create New Report and select Insights.
  3. Under Events, click Select Event, search for install and select it. Keep the metric as Total Events.

  1. Under Breakdown, click +, open Attributed By and select Ad Source.

  1. Click + again, open Attributed By, point to Ad Campaign ID and select Ad Campaign Name (or Ad Campaign ID).
  2. Check the attribution settings. The attribution model under the event defaults to Last Touch and the lookback window to 30 Days Lookback. Change them if your funnel needs it.
  3. Click Apply and choose a date range that starts after the go-live date, for example 7D or 30D. To see one row per campaign, switch the view from Line to Table.

  1. Click Save and give the report a name, for example Google Ads app installs or Meta app installs.

If installs show Google or Meta as the Ad Source along with your campaigns, attribution is working. If nothing shows up after three days, raise a support ticket with your Link ID or App ID and a campaign ID you expected to see. For how NVECTA counts installs in the first place, see Understanding app install counts in NVECTA, Firebase and Google Play Store.

Which event and attribute to use

What you want to seeEvent and metricBreakdown (Attributed By)
Installs from Google Ads or Meta compared with other sourcesinstall, Total EventsAd Source
Installs per campaigninstall, Total EventsAd Source, then Ad Campaign ID > Ad Campaign Name
Installs per ad set or adinstall, Total EventsAd Set ID or Ad ID
In-app conversions per campaignYour conversion event (for example, purchase), Total EventsAd Source, then Ad Campaign Name
Revenue per campaignYour purchase event, Sum of property set to your revenue property (for example, amount)Ad Source, then Ad Campaign Name

› A few tips:

  • Show only one ad network: under Filter, click +, open Attributed By, select Ad Source and include the Google or Meta value.
  • Try another attribution model: the attribution dropdown under the event offers Last Touch, First Touch, Participation, Linear and No Attribution.

Compare Google Ads and Meta with your other channels

Insights shows what your Google Ads and Meta app campaigns bring in. To see that next to what you spend on each network, and to compare them with your other ad channels, connect your ad accounts in NVECTA (Settings > Channels > Remarketing Ads; for Meta, use the Facebook tab) and set up ROAS analysis. The ROAS analysis recipe walks you through it.

Troubleshooting

What you seeLikely causeWhat to do
The link shows Unverified in Google AdsThe Link ID isn't added on the NVECTA side yet, or no app data has reached Google Ads.Wait for NVECTA support to confirm the setup. Check that you shared the Link ID for the right app and platform.
No Meta installs after three daysThe App ID isn't added on the NVECTA side yet, the Meta app is still in Development mode, has app restrictions or hasn't accepted the Advanced Mobile Measurement Terms, your Meta ads aren't delivering, or no one has installed the app from an ad yet.Check that the Meta app shows Live with no app restrictions and that your ads are running, then raise a support ticket with your App ID and a campaign ID you expected to see.
Ad Source shows not set for installsThe install wasn't attributed to an ad: it was organic, it happened before the integration was live, or it falls outside the lookback window.Choose a date range after the go-live date, or widen the lookback window.
Google Ads data shows for one platform onlyEach platform needs its own Link ID.Create a Link ID for the other platform and share it with NVECTA support.
Create & manage app ads with Meta Ads Manager is greyed outAnother use case is already selected on Add use cases.Clear the other use case, then select Create & manage app ads with Meta Ads Manager. If it still isn't available, contact NVECTA support before you create the app.
Meta doesn't let you switch the app to LiveRequired fields in App settings > Basic are empty.Fill in the fields Meta lists, usually Privacy policy URL, User data deletion, App icon and Category, then switch again.
https://graph.facebook.com/ with your App ID shows an errorThe app is still in Development mode, has app restrictions, or the ID isn't your App ID.Switch the app to Live, turn off the restrictions in App settings > Advanced, copy the App ID again from App settings > Basic, and test again.
The Meta app isn't linked to your business portfolioThe app was created without a business portfolio, or by someone without full control of it.Connect it under App settings > Basic > Business portfolio, signed in as someone with full control of the business portfolio that owns your ad account. Without full control, Meta sends a request to the business portfolio's Requests inbox, and the app is linked only after it is approved.
You chose the wrong use case when creating the appMeta doesn't let you remove a use case after the app is created.Create a new app and select Create & manage app ads with Meta Ads Manager on Add use cases (Part 1).

Conclusion

With your Link ID and App ID in place, NVECTA works as the measurement partner for your Google Ads and Meta app campaigns, and Insights shows which campaigns on each network bring in installs, in-app conversions and revenue.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article