CivicScience has developed a flexible framework for synchronizing digital identifiers between CivicScience and its partners whenever necessary or desired. Either of the two methods may be used for integration.
Pixel Method
In the first method, CivicScience provides a pixel to the partner. IdSync V3 (Partner Sync) does not automatically create cookies. It contains a partner parameter that allows CivicScience to control third-party alias storage.
A piece of code following the generalized pattern below is added to partner web pages:
<img src="https://www.civicscience.com/idsync/3?uid=<userId>&p=<partnerShortIdentifier>" width="0" height="0">
Or, when first-party integration is employed:
<img src="https://<firstPartyHostName>/idsync/3?uid=<userId>&p=<partnerShortIdentifier>" width="0" height="0">
JavaScript Method
For the second method, CivicScience gives the partner two short pieces of JavaScript and a short code used to identify the partner. The partner adds the code to their web pages.
- Add the following script tag inside the HTML
head
or just above the closingbody
tag.<script> const civSciAlias = "userID"; //partner's identifier for the visitor from CMS or other source const civSciPartnerId = "
partnerShortIdentifier
"; //IDSync Partner ID supplied by CivicScience </script> - Add the following script tag immediately below the
script
block in step 1.<script src="https://get.civicscience.com/idsyncjs/idsync.js" async></script>
Values
For both methods, the userId
is a unique identifier for the visitor known to the partner (such as a content management system or data management platform ID). It can be hashed or otherwise obscured; it is only necessary that it be unique per visitor.
The partnerShortIdentifier
is generated by CivicScience and supplied to the partner.