...
Form submissions are the primary means of converting Visitors from Anonymous to Identified. The S4S Cloud Send2CRM service form mapping defines which forms should perform identification and returns return the identifier with the response for a successful submission, which is then automatically applied.
...
Visitor identifiers can be set by calling the S4S Cloud send2crm library function:
Code Block | ||
---|---|---|
| ||
S4SCloud.analytics.visitor// Set a new identifier for the current visitor. // Will result in an immediate (async) update if changed. send2crm?.analytics?.visitor?.setIdentifier(visitorId); // Test whether the current visitor is identified. if (send2crm?.analytics?.visitor?.isIdentified()) { ... } |
The value provided must be a valid identifier for a Visitor record that exists within the S4S Cloud Send2CRM service for analytics functionality to work. If the identifier is not valid, the visitor will become anonymous after the attempted updated.
Identification via URL parameter
The Send2CRM client also supports setting identification for an existing visitor using the URL parameter s2cid. If this is found and has a non-empty value, send2crm will attempt to use this as the visitor identifier.
https://example.com/subscriptions?s2cid=a123b0000456789ABC
This may be useful for personalized external links, for example via email. If the recipient opens the link in a different browser or on a different device than when first identified, the identification will follow them. This could be used to implement subscription management or other online forms that require a known visitor.
Identification from other sources
Form submissions can be made programmatically for complex use cases. Check out the examples.
Personalization
Where server-side form mappings include fields that are marked for personalization, values are returned with successful responses and will be applied both identified and anonymous visitors. These values are limited to those defined for the form mapping only.