[SalesForce] ExactTarget API – Get campaign code from send id

I've written a small test C# application to extract tracking information (opens, bounces, clicks and unsubscribes) for a specified date from the ExactTarget API. Ultimately, this data will be imported back into a CRM system and will be used in reporting as well as future campaigns.

Each of the extract files contain a Send Id field which I know is the identifier for the particular send of the email campaign. However, I need to be able to relate this back to the campaign itself in the CRM system so that I can report on number of opens etc. per campaign and not per send (as the CRM system will know about the campaigns but not about the sends).

I've spent a fair bit of time looking through the API documentation and trying things, but I am struggling to see how I can either include the campaign id, code or name in the tracking extracts or, alternatively, make an additional API call to get the campaign id, code or name for a given Send Id. Sends and campaigns must be linked in the database behind the scenes as I can go into the ExactTarget web portal and see all the sends for a given campaign, but I need to get at this information through the API.

This is really quite urgent as I'm currently trying to finish off functional requirements for this project so if anyone can help me, it would be much appreciated.

Thanks

Best Answer

In a prior ExactTarget-integrated partner role, we had similar client instances where, if we needed to link a send to a customer-defined campaign name, campaign type, etc., we would enable the Additional_Email_Attributes business rule within the ExactTarget the account. *(This feature was initially built for the ExactTarget web analytics connectors; More info here: https://help.exacttarget.com/en-US/documentation/integrated_products__crm_and_web_analytic_solutions/web_analytics_connector/ )*

We would then be able to retrieve via the API all tracking details on a send, including those values entered into those Additional_Email_Attributes, and deliver aggregate the reporting details to the customer based on those addtl attributes—which were really just naming tags.

Would this accomplish your objectives?

Related Topic