This Sojern Documentation for Partners (“Documentation”) sets forth the technology requirements and policies that govern participation in Sojern’s partner programs. Sojern may update this Documentation from time to time via sojern.com and it is incumbent upon each partner to keep abreast of any and all changes hereto. Sojern reserves the right to modify the requirements and policies referenced herein at its discretion or restrict/deny participation and benefits based on the published Documentation. Updates to this Documentation will be delivered to the contact email address provided by partners and posted via sojern.com. The information within this Documentation is subject to the terms of the Sojern partner agreement between Sojern and each partner that references this Documentation. SOJERN DOES NOT PROVIDE ANY WARRANTIES REGARDING THIS DOCUMENTATION OR THE INFORMATION CONTAINED HEREIN AND SPECIFICALLY DISCLAIMS ANY LIABILITY FOR DAMAGES, INCLUDING, WITHOUT LIMITATION, DIRECT, INDIRECT, CONSEQUENTIAL, INCIDENTAL, AND SPECIAL DAMAGES INCURRED IN CONNECTION WITH RELIANCE ON THIS DOCUMENTATION.
Participants receive communications in the form of email messages and relevant partner information shared via sojern.com or other distribution channels. Communication topics vary and may include:
Contact your Sojern representative with questions or to request additional information.
Partners’ implementation of Sojern technology or other data collection methods is required to ensure a consistent and high quality experience with Sojern’s partner program. Partners transmit data such as when a website visitor performs an action (called an event) to Sojern, and these events are used to create custom audiences for ad targeting and for analyzing the effectiveness of conversion funnels. Partners are required to implement at least one of the following:
To add the Sojern Universal Pixel to partners’ websites, partners will need access to their website’s codebase. Partners can choose to add the codebase provided by Sojern on every webpage where they will track a website visitor’s actions. Partners can choose to track events by using one of Sojern’s predefined page types and/or pass a set of predefined object parameters to Sojern. For example, a “homepage” implementation will track events whenever a visitor arrives at a partner’s website’s homepage. Object parameters may be events associated with a vertical type, such as “flight” or “hotel”. Sojern will provide the tags or the form and format of events with any applicable guidelines. In the event a pixel or event fails to function properly and Sojern is unable to correct the issue, partners will remove the pixel from the domain and the event from the mobile application. Partners will inform Sojern of any site changes that impacts the pixel or event functionality.
A S2S integration requires the implementation of the Sync Pixel and a direct connection to a partner’s server. Partners will need to place the Sync Pixel on their websites, which requires that they have access to their websites’ codebase. Partners will need to implement a PostBack URL for the S2S calls to take place to pass events to Sojern.
Partners who wish to pass non-website and offline data to Sojern, such as data from call centers, walk-up bookings, or OTAs, can do so by uploading the offline data to a secure Google Cloud Storage or Amazon S3 storage bucket.
An integration with partners’ mobile application requires the implementation of a PostBack URL for a direct connection to partners’ server. If passing mobile application and device data to Sojern, partners are responsible for the following:
Partners who want to limit the use of data for certain ad campaigns due to competitors in the market or for other reasons, may work with Sojern to block certain Sojern-defined and available vertical and/or DSP channels. See the below table of the advertising verticals.
Sojern requires data to be encrypted by HTTPS/TLS protocol when in transit to Sojern and Sojern encrypts data at rest within our database.
When integrated with the Sojern Universal Pixel and providing email addresses to Sojern, the Sojern Universal Pixel will hash the email addresses at source (e.g. on the browser) before the hashed email addresses are transmitted to Sojern. At no point in time will Sojern receive email addresses that are not hashed when using the Sojern Universal Pixel. Sojern will hash email addresses using three hashing methodologies:
In the case where partners are providing email addresses through a S2S integration, batch upload, etc., or partners elect to hash email addresses on their own without using the Sojern Universal Pixel to hash, then SHA256 is a mandatory hash for email addresses provided to Sojern. Sojern encourages partners to also hash using MD5 and SHA1 methodologies.
Sojern does not have a direct relationship to users. Partners (or other parties responsible for data collection) are responsible for obtaining appropriate consents for the collection, use, and disclosure of user data to Sojern, and additionally, provide opt-out choices, including opt-outs of using the data for marketing and online advertising purposes. Partners may use a consent management tool (CMP) or other tools to manage consents and withdrawal of consents, and Sojern will endeavor to support the tools partners selected. If an identifier, like hashed emails, are not managed by a CMP tool, then partners are required to only provide email addresses where appropriate consent for such collection, use and disclosure have been provided by users. For the Sojern Universal Pixel, partners may direct users who want to withdraw their consent to Sojern’s opt-out tool made available at sojern.com/privacy/opt-out-data and we will replace all Sojern cookies with an "opt-out" cookie. The opt-out cookie persists for 5 years, unless the user clears their browser settings. A user who desires to delete their cookie ID or mobile ID would make the selection to delete their data from the same tool.
Sojern associates identifiers received from partners with data already owned by or licensed to Sojern to create custom audiences for ad targeting and for analyzing the effectiveness of conversion funnels. Upon any user request for deletion of a cookie or mobile advertising identifier when collected through a pixel integration, Sojern will immediately disassociate any related data linked to the identifiers from partners. Users also have the option to opt-out and request their data via the tools provided on sojern.com/privacy/ and further explained by the Sojern Privacy Policy, available at sojern.com/privacy/privacy-policy. Sojern will delete, destroy or anonymize identifiers that were provided by partners and stored in Sojern’s database within 90 days post-termination of the applicable contract with a partner.
Sojern uses data to create custom audiences for ad targeting. The audiences are aggregated and pseudonymized data. If the contract with a partner is terminated, the audiences may still exist in currently running ad campaigns (e.g. in-flight campaigns). Upon termination, Sojern will cease collection of data and will not add any partner-provided data to new audiences and campaigns. In-flight campaigns may continue to use existing audiences until campaigns end in due course.