[Feature] Add geography dimensions to shared data marts

[jstingey]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

Most of the ad platforms have the option to include geography data in the reporting API exports. This is often a very useful dimension for marketers.

Columns on the country/state/metro level would be excellent. If those columns were in the campaign report table all the better. If they needed to be their own table then that would be better than nothing. I'm sure some of the ad networks don't provide this info, in which case we should note that it will be null for those platforms.

Describe alternatives you've considered

The practical alternative now would be for marketers to spool up different campaigns for targeted geos and encode that in the utm_campaign string. This is far from ideal because it forces them to maintain parallel campaigns just to be able to differentiate geos.

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance and will schedule time during your office hours for guidance.
• No.

Anything else?

No response

[elanfivetran]

Hey @jstingey , thank you for opening up this feature request and your interest in the Ad Reporting package.

I definitely can understand the benefit that including geography dimensions would have for customers who are interested in breaking down their campaign metrics by geography. However, adding an additional grain would have a strong impact and can cause downstream breaking changes for our customers who are currently using any of our source specific ad reporting models currently. There are a number of additional campaign dimensions that can be added to our models but our team decided on the current selection to be the most universal and useful dimensions to break down performance by. Because of this, we don't feel that adding in an additional grain would beneficial to a majority of our customers.

That being said there are a couple of solutions that could help you accomplish your goal:

• As you mentioned, marketers can spool up different campaigns for targeted geos and encode that in the utm_campaign string.
• You can create a local copy of our package and add geography dimensions within the source models to group in your downstream output models.

I know this may not be the answer you wanted but hopefully it can help you get closer to your goal!

[fivetran-jamie]

Just an FYI that we're currently working on this! We'll have two new end models: one at the country level, the other at the region (ie state, province, metro area).

They'll both be at the month and campaign grain (though Facebook specifically will reflect account-wide metrics, as we currently don't have access to FB campaigns at the geo level). Moreover, we went with a monthly instead of daily grain to align with Linkedin Ads, as the geo-reporting data is only provided at the month there.

We've already rolled out the geo models to the individual platforms' packages, but you can expect them here in Ad Reporting in the following week or so