Meta Ads

Limited access

Connect Meta Ads spend with the store result

Daily campaign spend enters advertising analysis. Sales, COGS and returns come from other sources, so Netrivo also shows result completeness.

The connector has not completed live certification for public self-service.

What changes after connecting

Compare Meta with Google

See spend and contribution for both channels in the same reporting currency.

Detect an expired token

Separate authorization failure from no new data.

Assess campaigns after returns

Join ad spend with sales contribution reduced by available returns.

Meta Ads connection details in the Netrivo catalog.
Real Meta Ads configuration screen; credentials are hidden.

Meta Ads → data → result

  1. 01

    Ad account

    The token and ad account ID define report scope.

  2. 02

    Daily spend

    Spend is imported by campaign and day.

  3. 03

    Attribution

    Meta signals remain separate from store sales.

  4. 04

    Result after costs

    Advertising spend reduces campaign contribution once sales data is connected.

Data used by Netrivo

We show only fields actually supported by the integration. Not every account has to return every value.

DataImpactCondition
wydatkiDaily advertising costOnly when returned by the source
kampanieCampaign comparisonOnly when returned by the source
konwersjeConversion context with attribution-model limitationsOnly when returned by the source

What Netrivo can calculate

Meta spend in one model

Spend can be compared with Google Ads and sales without a manual spreadsheet.

Campaigns after margin

The result includes costs available in the workspace.

Token needing attention

Expired authorization is a distinct state, not silent data loss.

Campaign comparison with spend and result after costs.
The destination screen for this data type after a verified Meta Ads sync; visible values are demonstrative.

Why this connection is not available yet

The connector has not completed live certification for public self-service.

  1. 01The integration and required data scope are prepared.
  2. 02The real-account provider test is not complete yet.
  3. 03We therefore do not expose a form that cannot be completed.
  4. 04After a successful test, account verification, initial sync and coverage review will become available.

Connection requirements

  • A Meta ad account and its ID.
  • An access token with the required read scope.
  • A sales source and COGS for a complete result.

Limitations

  • Public self-service awaits completion of live certification.
  • Meta attribution is not the same as settled store sales.
  • Attribution-window changes may alter reported conversions.

Questions before connecting

How do I connect Meta Ads?

Choose Meta Ads, provide the ad account ID and token, then run the read test. Until live certification is complete, access may require controlled activation.

Does Netrivo import historical data?

Synchronization uses daily reports in the supported range selected for the connection.

How are connection credentials protected?

Credentials are sent only to the backend and stored encrypted. Tokens and secrets are never placed in the browser, public logs or screenshots.

What should I do when the connection test fails?

Confirm token scopes, ad account access and its ID. After renewing the token, reverify the existing connection instead of creating a duplicate.

What is currently outside the Meta Ads scope?

Public self-service awaits completion of live certification.

Related sources and analysis

Review available sources

The connector has not completed live certification for public self-service.

See available sources