Reference Reference Reference
    • Guided setup Guided setup for profiles and identity resolution.
    • Users Audiences, campaigns, journeys, activations.
    • Operators Configuration, SQL queries, analytics, databases.
    • Amperity API Programmatic access to your Amperity tenant.
    • Profile API Endpoints for unified customer profiles.
    • Streaming API Stream from external systems in real-time.
    • Amperity Bridge Share data directly with data warehouses.
    • Campaigns Send audiences to marketing workflows.
    • Destinations Send data to any downstream system.
    • Events Measure marketing efforts across channels.
    • Sources Pull data from any upstream system.
  • Reference
/
Open advanced search

Choose topic collections

Advanced search
Advanced search

ABOUT AMPERITY

  • Start here
  • Connected systems
  • Release notes

CONCEPTS

  • Sources
  • Stitch
  • Customer profiles
  • Audiences
  • Workflows
  • Activations

COMPONENTS

  • Activation IDs
  • AI Assistants
  • Amperity Bridge
  • AmpAI
  • APIs
  • Attribute types
  • Audience monetization
  • Connected systems
  • Consumer privacy
  • Customer Data Assistant
  • Dashboards
  • Data exports
  • Destinations
  • File formats
  • Home
  • Paid Media Measurement
  • Predictive models
  • Presto SQL
  • Profiles
  • Queries
  • Recent activity
  • Recommended Actions
  • Sandboxes
  • Settings
  • Segments
  • Segment Editor
  • Single sign-on (SSO)
  • Spark SQL
  • Workflows

RESOURCES

  • Glossary
  • Abbreviations
  • Naming conventions
  • Guided setup
  • System requirements

MORE RESOURCES

  • Help Center
  • Learning Lab
  • System Status
  • Amperity.com

ON THIS PAGE

  • How it works
  • Requirements
  • Set up a measurement courier
  • What data lands and how it refreshes
  • Query paid media performance with AmpAI
  1. Reference /
  2. Paid Media Measurement & Optimization

Paid Media Measurement & Optimization¶

Paid Media Measurement & Optimization brings your paid media performance data from Meta and Google into Amperity where it is available to AmpAI for analysis alongside your customer data.

There are two parts to it:

  1. Set up a measurement courier for Meta and/or Google. The courier pulls paid media performance data into your tenant on a daily schedule and adds it to the Customer 360 database.

  2. Ask AmpAI about paid media performance using natural language. AmpAI answers questions about your paid media data without requiring you to write SQL.

How it works¶

A measurement courier connects to Meta or Google using an authorized credential, and then pulls paid media performance data for a selected ad account into Amperity. The data lands in the Customer 360 database under a dedicated namespace for each platform, one for Meta and one for Google.

After the courier is set up, a courier group runs every day to keep the data current. Because the performance data lands in the Customer 360 database, it is available to AmpAI, which can use it to answer questions about paid media performance.

Requirements¶

Before you set up a measurement courier, make sure you have:

  • An authorized credential for the platform you want to measure–Meta or Google. You can reuse an existing credential, including one you already use to send data to a Meta or Google destination, so you do not need to create a separate credential for measurement. Add and authorize credentials from the Credentials page. See Credentials.

  • Access to the ad account whose performance data you want to bring into Amperity.

  • AmpAI enabled for your tenant, so that you can ask questions about paid media performance. See AmpAI.

Set up a measurement courier¶

Set up one measurement courier for each platform and ad account you want to measure. Add a measurement courier the same way you add any other courier, from the Sources page.

  1. From Sources, open the Couriers tab, and then click Add courier.

  2. For the plugin, select Facebook Ads Measurements or Google Ads Measurements.

  3. Enter a Name for the courier.

  4. Select the Credential type, and then select an authorized Credential.

  5. Select the ad account to measure:

    • For Facebook Ads Measurements, select an Account ID.

    • For Google Ads Measurements, select a Customer ID.

  6. Save the courier.

Tip

When you select a credential, Amperity automatically detects the ad accounts available to it and lists them for you to choose from, so you do not need to look up an account ID in advance.

Note

When you save the courier, Amperity sets up everything needed to keep the data current. It creates a courier group that runs once a day, creates the domain tables that the performance data lands in, and starts a first run that backfills approximately the previous twelve months of data. The first run can take longer than later daily runs.

To learn more about couriers and courier groups, see Couriers.

What data lands and how it refreshes¶

Paid media performance data lands in the Customer 360 database as domain tables, organized under a separate namespace for each platform, one for Meta and one for Google. Within each namespace, tables are grouped by the type of data they hold, including delivery data (such as spend, impressions, and clicks), conversion actions, and metadata. Tables are provided at campaign, ad set or ad group, and ad grain, along with breakdowns by dimensions such as age, gender, device, and placement.

The measurement courier keeps this data current:

  • The first run backfills approximately the previous twelve months of performance data.

  • After that, the courier group runs once a day to bring in new data and to refresh recent data as the platforms restate conversions.

Because these tables are part of the Customer 360 database, you can browse them alongside your other domain tables. See Custom domain tables.

Query paid media performance with AmpAI¶

After paid media performance data lands in the Customer 360 database, you can use AmpAI to analyze it with natural language—no SQL required. AmpAI recognizes the paid media tables and can answer questions about performance across Meta and Google.

Ask AmpAI questions such as:

  • “Compare the performance of Facebook and Instagram last month.”

  • “Rank my campaigns by return on ad spend.”

  • “Which campaigns show a declining click-through rate week over week?”

  • “Show me reach by campaign.”

AmpAI uses a set of standard paid media metrics as context when it answers, including return on ad spend (ROAS), cost per acquisition (CPA), click-through rate (CTR), cost per mille (CPM), cost per click (CPC), data freshness, and attribution status.

For how to ask questions, view the generated SQL, and work with results, see AmpAI and Customer Data Assistant.