Connect a source

What it is

Manta integrates with Meta, Google Ads, Google Analytics, Merchant Center, and LinkedIn, and syncs that data into the datastore. You connect a source in the Manta app, not by mounting a component in your own UI.

Open Integrations at /integrations, pick a source, and sign in with that platform. Starting the connection requires the org:integrations capability, which operators and organization admins have.

This page covers five of the sources in the Integrations catalog:

• Meta — Facebook and Instagram ad performance, audience, and creative data.
• Google Ads — campaign performance and spend across Search, Shopping, and PMax.
• Google Analytics — session, traffic, and conversion data from GA4 properties.
• Merchant Center — product feed and shopping campaigns from Google Merchant Center. An account whose latest Merchant Center terms aren’t accepted is listed but can’t be connected until they are accepted in Merchant Center.
• LinkedIn Ads — campaign performance and spend across your LinkedIn Ads accounts. This entry is listed only for the hiremanta-com realm.

Import

Nothing to import. After the sync, read the entities from the datastore with the schemas you generate for it.

Example

After you pick the accounts or properties, the app tells you what it will load:

• Meta: “We’ll start loading your campaigns, ads, creatives and their performance history.”
• Google Ads: “We’ll start loading campaign performance and spend for the accounts you picked.”
• Google Analytics: “We’ll start loading session, traffic and conversion data for the properties you picked.”
• Merchant Center: “We’ll start loading products and promotions for the accounts you picked.”
• LinkedIn Ads: “We’ll start loading campaign performance and spend for the accounts you picked.”

Request

The app opens a same-tab link on your deployment. The datastore id is the datastore query parameter:

GET /oauth/meta/start?datastore=your-datastore

Google Ads uses /oauth/google-ads/start, Google Analytics uses /oauth/google-analytics/start, Merchant Center uses /oauth/google-merchant-center/start, and LinkedIn uses /oauth/linkedin/start, each with the same datastore parameter.

Response

The start route does not return a JSON body.

A caller who may connect is redirected (302) to the provider’s sign-in. The Location is the one the Manta API returns for that provider.

A caller without org:integrations is redirected to Integrations instead. For Meta that location is:

/d/your-datastore/integrations?oauth_provider=meta&oauth_error=start_failed

The page then shows Couldn't connect Meta. With no error description, the text is Something went wrong completing the connection. Please try again. Google Ads, Google Analytics, and LinkedIn use the same query shape, with oauth_provider set to google, google-analytics, or linkedin.

After you finish sign-in and pick accounts, the app shows Importing your Meta data (or Google Ads, Google Analytics, or LinkedIn Ads) and the notice above. The first import can take a while. The data shows up when the import finishes, and you can close the dialog before then.

The datastore then has a connected account for the grant, pointing at the provider’s entity:

• a Meta ad account (meta:AdAccount), with its ad sets, ads, and creatives
• a Google Ads customer (google:Customer), with campaigns and a dated performance snapshot for each campaign and day (google:CampaignInsight)
• a GA4 property (ga4:Property), with daily totals, traffic sources, and product and category performance
• a LinkedIn ad account (linkedin:AdAccount), with campaign groups, campaigns, creatives, and a day of analytics per campaign and per creative