Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Forms

Form submissions are the primary means of converting Visitors from Anonymous to Identified. The S4S Cloud service form mapping defines which forms should perform identification and return the identifier with the response for a successful submission, which is then automatically applied.

Programmatic identification

Visitor identifiers can be set by calling the S4S Cloud library function:

S4SCloud.analytics.visitor.setIdentifier(visitorId);

The value provided must be a valid identifier for a Visitor record that exists within the S4S Cloud service for analytics functionality to work.

Identification via URL parameter

The S4S Cloud client also supports setting identification for an existing visitor using the URL parameter s4scid. If this is found and has a non-empty value, S4S Cloud will attempt to use this as the visitor identifier.

https://example.com/subscriptions?s4scid=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.

  • No labels