Configure Microsoft Ads as a Source in your Pipeline

Perform the following steps to configure your Microsoft Ads Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Microsoft Ads.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Microsoft Ads Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Connect to your Microsoft Advertising account section, click Authenticate your Microsoft Ads account, log in to your Microsoft Ads account, and click Allow to grant Hevo access to your account.

   

7. In the Configure Source screen, specify the following:

   

   • Account Selection: Choose whether to sync data from all accessible accounts or only specific accounts.

     • Sync All Accounts: Hevo syncs data for all ad accounts accessible to your authorized Microsoft Ads account, including any accounts added later.
     • Sync Specific Accounts: Hevo ingests data only for the accounts you select from the Accounts to sync drop-down.

   • Additional Settings

     • Show Advanced Options: Enable this toggle to configure the following additional settings:

       • Rollback Window Size (days): Specify the number of days for which Hevo re-fetches previously ingested reports to capture updated report data within Microsoft Ads’s 30-day conversion-attribution window. Default: 35 days.

         This value should be greater than the conversion window configured in your Microsoft Ads account.

   • Historical Sync Time Frame: The duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default: 6 months.

8. Click Test & Continue to test the connection to your Microsoft Ads Source.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Selecting a parent object automatically includes all its associated child objects for replication. Child objects cannot be selected or deselected individually.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For all objects supported by this connector, Hevo ingests only the incremental data in subsequent Pipeline runs:

• For all core objects, Hevo detects incremental changes using the modified_time field.

• For all reports, Hevo detects incremental changes using the date field.

For Report objects, Hevo also re-fetches data from the number of days specified in the Rollback Window (days) field during each sync. This captures any updates made to previously ingested report data and keeps your Destination up to date. Events ingested through data refresh are not billable.

Microsoft Ads enforces a rate limit on the number of calls that can be made to its APIs in a given time period. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Core Objects

Reports

Reports provide metrics about user activity and ad performance. To support both daily and hourly analysis, Hevo creates two Destination tables for each report.

---