Hi,
We are looking to generate a campaign execution/statistics report and I'm looking to extract campaign execution metadata via API's.
The two fields Im interested to extract from every campaign execution are:
i. CampaignID
ii. CampaignRunID
I know there are few lead activities which pulls this information with each activity record. But some activities like "Add to List" doesn't provide CampaignRunID.
Is there a way I can just pull the campaign execution metadata (campaignID, CampaignRunID association) via some API?
This will allow my custom report to read this metadata and merge all activities together to identify their relations to different campaign executions.
Thanks in anticipation !
There's no dedicated endpoint for this.
(Also note that Add to List need not be associated with a Campaign.)
Thanks for confirming.
I'm actually using static lists as a way to capture control group in a campaign and then doing reporting after merging this as an activity.
So what we are saying is that there is no way we can identify CampaignRunID associations with campaigns we run on a regular basis?
So what we are saying is that there is no way we can identify CampaignRunID associations with campaigns we run on a regular basis?
I don't know exactly what you mean by "identify" but you're talking about unique IDs, not user-managed metadata. So no, you can't independently query the Run ID of last Tuesday's 4pm send.
In short I'm trying to identify campaign wave using some logic on CampaignID and CampaignRunID.
AFAIK, the CampaignRunID is globally incremented on every campaign run within one Marketo instance and I'm somehow trying to identify which CampaignRunID belongs to which Campaign.
You can't query this, because there is no corresponding endpoint.
Get the feeling that instead of starting from what Marketo can do, your project started from a concept that can't fit with Marketo's technical architecture. Perhaps you should go back to the business requirements stage to avoid ongoing XY problems.
Thanks Sanford Whiteman for all the help on this.
Yes I agree, we need to revise our reporting requirements here as this is something which can't fit in using Marketo.
Now that I have confirmed this limitation, I can work with my team to re-evaluate and come up with a different approach.
Thanks again !