Impact

introduction the impact destination enables server side integration with impact's affiliate marketing and partnership management platform it sends event data to impact's tracking apis to measure affiliate driven conversions and website activity connecting impact as a cdp destination allows chord to forward conversion an dpage events and customer identifiers to impact so your marketing and acquisition teams can benefit from more accurate reporting of affiliate driven conversions and activity getting started impact is a cloud mode destination , meaning chord sends events pass through the chord cdp and are sent from the cdp through to impact before connecting, ensure you have an active impact account campaign id your impact campaign/program id found in the top left corner of the impact dashboard account sid used for authentication, this can be found in your impact account settings api key used for authentication, this can be found in your impact account settings event type id custom event type id for conversions connecting to the impact cdp destination log into the chord data platform navigate to the cdp open the destinations tab click add and select impact from the destination catalog provide a recognizable destination name (e g , “impact – production”) enter your campaign id, account sid, api key & event type id selet/enable any relevant settings for events you wish to pass through enable page events enable identify events enable all track events add any relevant custom event names to trigger conversions and/or to trigger page load track events add any addition custom parameter mapping and/or custom product field mapping click create to activate the destination chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination the chord tracking plan events used by the impact destination are chord tracking event destination event order completed conversion / action identify page load, requires enableidentifyevents true page page load, requires enablepageevents true all track events page load, requires enabletrackevents true before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream