Open gmzgian opened 8 months ago
@gmzgian do you have other custom reports or only this one? What destination are you using and vesion?
Hi @marcosmarxm, thanks very much for giving it a look.
customconversion_performance_daily
, Pivot Category: CONVERSION; Time Granularity: DAILY. This one yields wrong data.
customcampaign_performance_report_daily
, Pivot Category: CAMPAIGN; Time Granularity: DAILY. I get correct data with this one though.
BigQuery v2.4.11
and Postgres v0.6.3
. I get the same exact data discrepancy with both destinations when creating the CONVERSION Custom Ad Analytics Report.Let me know if I can provide anything else. Gian Marco
Connector Name
source-LinkedIn Ads
Connector Version
0.6.8
What step the error happened?
Other
Relevant information
Hi there, I get inaccurate conversion data when building a Custom Ad Analytics Report from my LinkedIn ads source in Airbyte. Pivot Category: CONVERSION; Time Granularity: DAILY. I need that to find out the conversion names (the id comes from the
pivotvalues
in the table a get from the custom stream), their overall conversions (externalwebsiteconversions
), conversion clicks (externalwebsitepostclickconversions) and conversion views (externalwebsitepostviewconversions
). All grouped by each creative ideally. However, the data I get from this stream is totally incorrect compared to what I actually have on Linkedin Ads.The odd thing is, I actually get correct conversion data when I build another Custom Ad Analytics Report from my LinkedIn ads, but this time I use: Pivot Category: CAMPAIGN; Time Granularity: DAILY.
So, there is something not working when the Pivot Category = CONVERSION.
I noticed the Conversion stream might use the wrong key as a primary key for data replication. For both Conversion and Campaign streams, the
pivotValue
is equal tourn:li:sponsoredCampaign
, which is correct only for the custom Campaign stream. For the custom Conversion, theurn:lla:llaPartnerConversion
should be used aspivotValue
. Wrong key is leading to the problem of some values being overwritten as Deduped strategy, I believe.Relevant log output
No response
Contribute