Insider One

introduction insider one is a cross channel marketing automation platform for personalizing user experiences and triggering journeys across web, mobile, and messaging channels this destination sends events to insider one using the server side upsert api , making it immune to ad blockers and browser restrictions getting started this is a cloud mode destination you will need account name — your insider one account name found in inone panel > settings > inone settings > account preferences api key — your insider one api key found in inone panel > settings > preferences > integration settings connecting to the insider one cdp destination 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 log into the chord data platform navigate to the cdp click the "add" button next to destinations select insider one from the destination catalog enter the destination name, account name , and api key optionally configure treat email as identifier — if enabled, the user's email address is included as an insider one identifier in addition to the user id treat phone number as identifier — if enabled, the user's phone number is included as an insider one identifier click "create" to connect events event mapping chord event type insider one api notes identify post /api/user/v1/upsert updates user attributes and identifiers; no event recorded track post /api/user/v1/upsert sends one or more events; user attributes updated simultaneously page post /api/user/v1/upsert sent as a page view event unsupported event types (e g group , alias ) are silently dropped ecommerce event name mapping chord ecommerce track event names are translated to insider one's reserved event names chord event name insider one event name product viewed product detail page view product list viewed listing page view product added item added to cart product removed item removed from cart cart viewed cart page view order completed confirmation page view checkout started checkout page view checkout step viewed checkout page view user registered sign up confirmation all other event names are converted to snake case (e g button clicked → button clicked ) identify events identify events update user attributes in insider one no event entry is recorded insider one field chord source (priority order) notes identifiers uuid userid primary user identifier identifiers email context traits email > traits email only included if treat email as identifier is enabled identifiers phone number context traits phone > traits phone > traits phone number only included if treat phone number as identifier is enabled identifiers custom segment anonymous id anonymousid always included as a custom identifier attributes traits merged with context traits reserved attribute names mapped directly; others placed in attributes custom track events track events send one or more event entries to insider one alongside updated user attributes insider one field chord source (priority order) notes identifiers same as identify see identify events above attributes context traits merged with traits see attribute mapping below events\[] event name event (translated via ecommerce map) see event name mapping above events\[] timestamp timestamp iso 8601 format events\[] event params properties reserved param names mapped directly; others placed in event params custom if properties products is a non empty array, each product is expanded into its own event entry top level properties (e g currency , order id ) are merged into each product's event params page events page events are sent as page view events insider one field chord source (priority order) notes identifiers same as identify see identify events above attributes context traits merged with traits see attribute mapping below events\[] event name (hardcoded) page view events\[] timestamp timestamp iso 8601 format events\[] event params url properties url > context page url events\[] event params referrer properties referrer > context page referrer events\[] event params remaining properties reserved params mapped directly; others in event params custom attribute mapping chord trait names are normalized to snake case and mapped to insider one's reserved attribute names where applicable unrecognized traits are placed in the attributes custom object chord trait insider one attribute firstname name lastname surname address city city address country country locale locale (hyphens converted to underscores, e g en us → en us ) all other reserved attributes mapped directly (see list below) reserved attributes mapped directly email , phone number , age , birthday , name , gender , surname , city , country , app version , idfa , model , last ip , carrier , os version , platform , timezone , locale , gdpr optin , email optin , sms optin , whatsapp optin , language event parameter mapping chord property names are normalized to snake case known property aliases are remapped to insider one's reserved event parameter names chord property insider one event param order id or cart id event group id category taxonomy (wrapped in array if not already) image url product image url reserved event parameters mapped directly campaign id , campaign name , url , product id , user agent , taxonomy , name , variant id , unit sale price , unit price , quantity , product image url , event group id , referrer , currency all other properties are placed in event params custom testing and validation after connecting the destination trigger a test event from your storefront or use the live events tab in the chord cdp in insider one, navigate to inone panel > audience and verify the user profile was created or updated check event history under the user profile to confirm events were received review the live events diagnostics in the chord cdp for any api errors or credential issues use cases personalize onsite experiences using purchase history and loyalty tier attributes synced from chord trigger re engagement journeys when chord sends a track event like subscription cancelled or cart abandoned build high value segments in insider using enriched customer attributes from chord (e g , ltv tier, acquisition channel) suppress messaging by syncing opted out users from chord to keep insider audiences up to date activate post purchase flows by sending order completed events with product and revenue details best practices always include an identifier insider needs at least one identifier (email, phone, or uuid) to match or create a profile events without identifiers will be dropped use consistent user ids ensure the userid sent from chord matches the uuid insider already has on file for existing profiles format phone numbers correctly include the country code (e g , +14155550123 ) incorrectly formatted numbers will not match existing profiles filter events deliberately sending all track events is rarely necessary start with high signal events (e g , order completed , product viewed ) and expand from there monitor delivery logs after launch check for 4xx errors in the first few days — these typically indicate a mapping or credential issue troubleshooting data not sending problem events are not appearing in insider one after the destination is enabled confirm the destination is enabled in chord verify your api key and account name are correct — a single character error will cause all requests to fail check the live events diagnostics in the chord cdp for error responses (look for 401 or 403 status codes) confirm that the event types you want to send (identify, track, page) are being emitted by your storefront missing attributes problem user profiles appear in insider one but expected attributes (e g , custom traits) are missing custom traits not in insider's reserved attribute list are nested under attributes custom verify the attribute name in insider includes the custom prefix check whether the attribute exists in insider's schema new custom attributes may need to be created in insider before data can be written to them confirm the trait is present on the identify event being sent from chord by inspecting the live events payload duplicate users problem insider one is creating multiple profiles for the same customer confirm that identify events consistently include the same identifier (email or uuid) inconsistent identifiers cause insider to create separate profiles if your store captures both anonymous and logged in sessions, ensure an identify call is sent when a user logs in so insider can merge the profiles check that phone numbers are formatted consistently — a mismatch (e g , with and without country code) can prevent profile matching