CAMPAIGN_SHARED_SET report doesn't have SharedSetId?

30 views
Skip to first unread message

Emmanuel

unread,
Mar 17, 2016, 8:28:36 AM3/17/16
to AdWords API Forum
Our understanding is the CAMPAIGN_SHARED_SET report details the associations between shared lists and campaigns.

Is there a reason why this report doesn't have the main ID of the shared list SharedListId?  The report has only SharedListName which we can use to retrieve the relevant shared list but it sounds strange that, while all other reports use IDs, this one report relies on a string identifier and not the main shared list ID.


Josh Radcliff (AdWords API Team)

unread,
Mar 18, 2016, 8:43:19 AM3/18/16
to AdWords API Forum
Hi,

Excellent point -- this report really should have the SharedSetId. I'll pass this along to our reporting team.

Thanks,
Josh, AdWords API Team

Emmanuel

unread,
Mar 25, 2016, 2:28:49 AM3/25/16
to AdWords API Forum
Thanks Josh.

Are there any timescales roughly when you think the SharedSetId field can be added to CAMPAIGN_SHARED_SET?

We're having lots of issues using SharedListName instead of SharedSetId in AWQL as some strings cause the AWQL query to break.

Thanks

Josh Radcliff (AdWords API Team)

unread,
Mar 25, 2016, 8:57:17 AM3/25/16
to AdWords API Forum
Hi,

I don't have a timeline just yet, but could you provide an example of a string that causes issues with the AWQL query, along with the query and the error you're encountering?

Thanks,
Josh, AdWords API Team

Emmanuel

unread,
Mar 26, 2016, 2:28:00 AM3/26/16
to AdWords API Forum
We managed to fix the issue, thanks.

However, to be consistent with how reporting works in general, it would be great if the SharedSetId is added to this report.

Thanks

Josh Radcliff (AdWords API Team)

unread,
Mar 28, 2016, 8:41:46 AM3/28/16
to AdWords API Forum
Hi,

Glad to hear you were able to resolve the immediate issue. I'll continue to follow up on having the ID field added to the report and will update this post when I have more information to report.

Thanks,
Josh, AdWords API Team
Reply all
Reply to author
Forward
0 new messages