Bing Ads source

Bing Ads is a pay per click (PPC) advertising platform that works on both Bing and Yahoo search engines. It allows marketers to track and monitor their ad campaigns, resulting clicks, CTRs, and more.

All the Cloud Extract sources support sending data only to a data warehouse destination.

Getting Started

1. Log into your RudderStack dashboard.
2. Go to Sources > New source > Cloud Extract and select Bing Ads from the list of sources.
3. Assign a name to your source and click Continue.

Connection settings

Next, configure the following dashboard settings:

• Tenant ID: Enter the Tenant ID of your Microsoft Advertising developer application. It is recommended to set it as common unless you need a different value.
• Connect with Bing Ads V2: Click this button to give RudderStack the required permissions to access your Bing Ads account.
• Developer Token: Enter your user developer token. Refer to the Microsoft documentation for more information on obtaining the developer token.
• Reports replication start date: Select the date from when RudderStack should ingest your Bing Ads data. RudderStack will not replicate any data before this date.

Destination settings

The following settings specify how RudderStack sends the data ingested from Bing Ads to the connected warehouse destination:

• Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Bing Ads data into it.

Note that RudderStack does not add special characters like - or _ to the prefix by default. Hence, you need to specify it while setting the prefix.

• Schedule Settings: RudderStack gives you three options to ingest the data from Bing Ads:
  • Basic: Runs the syncs at the specified time interval.
  • CRON: Runs the syncs based on the user-defined CRON expression.
  • Manual: You are required to run the syncs manually.

For more information on the schedule types, see Common Settings.

Selecting the data to import

You can choose the Bing Ads data you want to ingest by selecting the required resources:

The below table mentions the syncs and primary keys supported by these resources from Bing Ads to your warehouse destination:

Bing Ads is now configured as a source. RudderStack will start ingesting data from Bing Ads as per your specified schedule and frequency.

You can further connect this source to your data warehouse by clicking on Add Destination:

Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.

FAQ

How does RudderStack count the events for Cloud Extract sources?

RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.

Is it possible to have multiple Cloud Extract sources writing to the same schema?

Yes, it is.

We have implemented a feature wherein RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.

How does RudderStack set the table name for the data sent via Cloud Extract sources?

RudderStack sets the table name for the resource you are syncing to the warehouse by adding rudder_ to the Table prefix you set while configuring your Cloud Extract source in the dashboard.

For example, if you set test_ as the Table prefix in the dashboard, RudderStack sets the table name as test_rudder_<resource_name>, where <resource_name> is the name of the resource you are syncing (for example, contacts, messages, etc.).

Note that RudderStack does not add the character _ to the prefix by default. Hence, you need to specify it while setting the prefix.

Questions? Contact us by email or on Slack