[Feature] Add conversion_history to dbt_linkedin_ads Package

[siunmarkey]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

Hi Fivetran team,

We're using the Fivetran LinkedIn Ads connector and have the conversion_history table syncing into our raw schema (raw_db.fivetran_linkedin_ads.conversion_history).

However, this table is not currently included in the dbt_linkedin_ads package. Would it be possible or are there any plans to add this table to the package?

Thanks!

How would you implement this feature?

Create a staging model: stg_linkedin_ads__conversion_history

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance.
• No.

Anything else?

No response

[fivetran-joemarkiewicz]

Thanks @siunmarkey for opening this feature request! This is something we could integrate into the upstream data models. I am curious to know how you would plan to leverage this table in combination with the other reports? Or are you looking to have this table added for other reasons?

[siunmarkey]

Hey @fivetran-joemarkiewicz thanks for the quick reply!

Our main use case would be to combine the conversion_history table with the conversion_associated_campaign table to get a clearer picture of which campaigns are driving specific conversions.

Apologies I should have included conversion_associated_campaign in my initial ticket! Lmk if you need any more info.

[fivetran-joemarkiewicz]

@siunmarkey thanks for your reply, in addition to combining the conversion_history table with the conversion_associated_campaign table, which fields would you be most interested in bringing through to enrich the data? We can explore adding this table into the source and end models, but we would want to make sure we bring in specific fields that are useful for customers to leverage for their reporting needs. Thanks!

[siunmarkey]

Hey @fivetran-joemarkiewicz, apologies for the delayed response!

I have looked into this a bit more and think the best approach would be to add the following

• AD_ANALYTICS_BY_CREATIVE_WITH_CONVERSION_BREAKDOWN table (to link each creative_id to conversion_id)
  fields:
  CONVERSION_ID
CREATIVE_ID
DAY
EXTERNAL_WEBSITE_CONVERSIONS
EXTERNAL_WEBSITE_POST_CLICK_CONVERSIONS
EXTERNAL_WEBSITE_POST_VIEW_CONVERSIONS
ONE_CLICK_LEAD_FORM_OPENS
ONE_CLICK_LEADS

• CONVERSION_HISTORY (to get the conversion name and type associated with conversion_id e.g 'sign up', 'submit application')
  fields:
  ID
NAME
TYPE

Essentially the end goal would be to have the following report:
CONVERSION_ID
CAMPAIGN_ID
CAMPAIGN_NAME
CREATIVE_ID
DAY
CONVERSION_NAME
CONVERSION_TYPE
TOTAL_WEB_CONVERSIONS
TOTAL_POST_CLICK_CONVERSIONS
TOTAL_POST_VIEW_CONVERSIONS
TOTAL_ONE_CLICK_LEADS