SAP Customer Data Cloud Positions

Lite Registration

Skip to end of metadata
Go to start of metadata


Lite Registration is a way for users to engage with your site and content without having to register with a full account, using only their email address and no password. Users can later choose to convert their passwordless accounts into a fully registered account, so as to access exclusive member content, place orders, or subscribe to a service, for example. Lite Registration is often the first step of building a trust-based relationship between your site and the site users, starting the customer journey early on. Use Lite Registration in newsletter sign-up flows as part of your newsletter management, and as a lead generation tool in any scenario where users can submit their emails without registering (contest participation, online polls, campaigns etc.). Using Customer Identity (RaaS) and/or Customer Consent is a precondition to enabling Lite Registration in your account.

For customers who use Enterprise Preference Manager, note that Subscriptions are available for both fully registered users and guest users (lite registrations). 

Lite registration features include the following: 

  • Out-of-the-box lite registration screens that can be highly customized using Gigya’s UI Builder.
  • Clear opt-in and opt-out flows for complying with privacy regulations.
  • Improved quality of data: data is not lost when users convert from lite registrations to fully registered accounts.
  • Increased user satisfaction as all user data is saved from the get-go, no need to refill forms that have already been filled in, preferences and identity are saved and can be used to show users the content in which they are interested.
  • Drives higher user acquisition rates with screens that combine compelling offers and low-barrier opt-ins.
  • Full support for exporting and importing subscriber data to third-party platforms, such as Email Service Providers (ESPs), either with IdentitySync (Gigya’s ETL service) or using
  • Support for giving lite users full control of their data, using the Lite Preferences Center.

Instructional Video

If you have an SAP logon, you can watch a video about Lite Registration, here.


Lite AccountCreated when a site visitor completes a non-authenticated, Lite Registration flow. The information they contain is merged into email accounts, for a cohesive view of the user.
Full AccountCreated when a site visitor completes the full registration flow (regardless of whether or not the account is pending verification). These users can register with a social identity, or create a password for your site. Either way, they are authenticated users. In the context of Lite Registration, full account data is merged into the corresponding email account, every time a accounts.setAccountInfo call is made for that account. Note that a fully registered user can complete the lite registration flow like any other site visitor.
Email AccountProvides a view of users that is based on their identifier, merging data from both lite registration and fully registered accounts. Note that data is merged from full accounts or lite registrations into this email accounts and not vice versa, with the exception of subscription data that is shared in real time between account types. An email-based view is enabled only when Lite Registration or Subscription Management are enabled in your Gigya site.

Subscriptions Object

* Available only with Enterprise Preference Manager

Stores subscription data for a designated mailing list. The data stored for each subscription includes the subscription status of the subscribed user (true/false), a timestamp for the status change, and custom tags. Note that subscription data is the only type of data shared between all accounts. Therefore, you can retrieve subscription data of fully registered users and of lite registrations.


One View for All Customer Data

The email account is a merged view of all data that pertains to a specific email address. Therefore, Lite Registration enables deduplication not only of your Gigya data, but of all your user data stored externally (whether in ESPs, spreadsheets or other external systems). Since these are not fully registered users, there is no need to pass a user password between databases. 

Lite and Full Registrations

When users performs Lite Registration, regardless of whether these users are already fully registered or not, they are not required to create a password, but only to provide their email address. Each lite registration is later passed on to an email account, updating an existing account or creating a new one. 

Gigya offers built-in capabilities for tracking the customer's journey throughout your site as an evolving relationship. When users perform a lite registration to your site, an email account is created, to which a unique identifier is assigned (UID). When, later down the line, the same email address is used to fully register to your site (via Customer Identity), Gigya automatically assigns it the same UID. In regards to the relationship between lite and full registrations, the following is supported:

  • Account progression from lite to full: When a new full account is created, either by standard registration, or social or federated login, and the email address used for creating that full account already exists for an email account, the newly created full account will share a UID with the existing email account.
  • When a fully registered user changes their main email address, and that email address is associated with a lite registration (email account), then the email address will change for that email account as well.
  • When a user account is deleted, all corresponding accounts associated with that email address are deleted. If the email verification policy is turned on, only email accounts associated with verified emails will be deleted. Note that this behavior supports privacy compliance.
  • Using the UID in third-party integrations prevents passing personally identifiable information (PII) for better user privacy and security.



Create and Customize Lite Registration Screens

Any new screen-set collection created in the Console will include the LiteRegistration screen-set.

You can customize the screens in either of the following ways:

Map a Subscription Field Using Metadata

For customers who use Customer Consent: If you are adding a subscription that requires double opt-in, you should add a subscription widget to your lite registration screens. For more information, see Subscription Management: Implementation. This section is a guide for mapping a subscription to a lite registration screen, when you don't want to include a checkbox, but just a "Subscribe Me"-type button. 

Lite Registration can be used to create any screen that requests the users’ email without a password ("lead generation screens", for example, to unlock content, sign up for a competition, vote, etc.). In this case, there may be no need to map a field to any subscription. 

One common scenario of Lite Registration would be to have a subscription screen where the user opens a "subscribe me to your newsletter" screen (or it pops up automatically), and needs only to pass their email and press "submit", with or without a "terms of use" checkbox.This means that the field that actually subscribes the user (passes "true" to the isSubscribed field of the relevant subscription) is not visible to the user: they do not need to check a box or choose the subscription, since the details telling them of the subscription are in the UI of your site. To set this up, we recommend using a metadata control, that is always hidden and is not influenced by existing data in the database, as opposed to form fields, whose values could potentially be overriden by existing data, even if you create them with a default value. 

We suggest the following implementation: 

  1. Open the Lite Registration screen for editing in the UI Builder. 
  2. Edit the screen's texts and appearance as needed. You can choose to delete the default "Weekly Subscription" checkbox.
  3. Drag a "Metadata" control into the screen. 
  4. Open the "Mapped Field" dropdown. Under "Subscriptions", select Add
  5. Give your subscription a name and click Add
  6. Choose the JavaScript expression value format, and set the value to 'true'. 

    The screen in the UI Builder now looks like this: 
  7. Save your changes.


Lite Registration Required Fields

Lite registration screens have behavior that differs from all other screen-sets in regard to required fields.

Lite registration will succeed even if there are required fields within your site's schema that have not been completed for the user; There is never a Registration Completion form triggered by a lite registration screen. If you need a field to be completed when users fill out a lite registration form, you must include the field on the lite registration submission form, and if it is not already required in the site's schema, select the Required: When Visible option in the Schema section of the UI Builder Properties panel. 


This will force the user to complete the field prior to submitting the lite registration form.




Add Lite Registration Screens to Your Site

For a guide on adding Gigya screens to your site, see Customer Identity Quick Start Guide

Lite Account Creation

To summarize, a lite account can be created using Screen-Sets, or using API calls. 

Using Screen-Sets

A lite account is created when a user submits their email in the LiteRegistration screen-set.

Using APIs 

The API flow for creating a lite account: 

  1. Call accounts.initRegistration with the following parameters
    • isLite: true
    • callback: function that passes response data from this call to accounts.setAccountInfo
  2. Call accounts.setAccountInfo with the following minimum parameters received from initRegistration.
    • regToken
    • profile: {email:"The user's email"}
    • Optional: any other 'profile' or 'data' fields

Lite Account Progression

Lite account progression can be facilitated by a screen-set or API-based flow, or result from a site policy. At the moment of progression:

  • Lite data is copied over to the full account, including consent and subscription information. 
  • If the full registration includes data that is different from the existing lite data (e.g. the "lite" name is Jen, but the "full" name is Jenny), the full registration data will take precedence (in this case, Jenny). 
  • After the account progression, lite interactions for that user will be saved as usual only to the emailAccounts namespace, except for consent interactions, which will always be copied into the full account. 
  • An "Account Progressed" webhook is fired.

Screen-Set Flow

You can use the Lite Account Progression screen in the registration login screen-set to progress a user from a lite account to a full. Since the screen receives a token that identifies the user's email, all the user needs to do is enter a password to complete their progression to fully registered users. You can trigger the screen on the Lite Preferences Center, or on another page of your website to which the user is redirected from an email link. 

  1. In the Screen-Sets page of the Console, make sure your Lite Account Progression screen has the "Progression" behavior defined: 
  2. If you are using the Lite Preferences Center, you can trigger the Lite Account Progression screen on the same page as the preference center, to enable users to complete their progression there. Since the lite preferences flow includes passing the relevant token to the preferences center via the Lite Preferences Center email template, it is passed into the screen as well. 
  3. If you wish to display the Lite Account Progression screen on a separate page of your site, the flow is as follows: 
    1. Call accounts.getLiteToken to receive the lite user's token. 
    2. Use your emailing system to send the relevant account progression email to the user that includes a link to the page on which your account progression screen is hosted. The link should include the token as a query string parameter, in the following format: `gig_regToken=123456`. 
    3. On the relevant page of your site (to which the user is redirected), call the Lite Account Progression screen as follows:


API Flow

You can pass the lite registration token to the accounts.register API to trigger account progression for this user. 

  1. Call accounts.getLiteToken with the user's email address to receive a token. 
  2. Pass that token in the regToken param of accounts.register.


Auto Progression Policy

You can turn on a policy to handle what happens when a lite user with a specific email address, performs a full registration on your website with the same email, by setting the progression policy to "automatic" in the Console Policies page:


When a lite user performs full registration with the same email address and the policy is turned on, the user will progress from lite to full, as described above.




  • Because full registration is a multi-step process, there is some latency between the moment of full registration and the data merge.
  • If the progression policy is set to "automatic", when a full account changes their field to that of an existing lite identity, it is considered a lite account progression.
  • Birth date fields (birth year, month and day) and name fields (first and last names) are considered one field from a data merge perspective. For example, if a lite identity contains the birth day, month and year, and at the moment of full registration only the birth year is passed for that account, the "lite" birth day and month will be deleted.

View and Update Lite and Subscription Data

View lite and subscription data using the following:

Updating lite data: 


Query examples:


Retrieve all email accounts: 

 SELECT * FROM emailAccounts

Retrieve all subscribers to a specific newsletter, from email accounts: 

 SELECT * FROM emailAccounts WHERE subscriptions.<NEWSLETTER-NAME>.email.isSubscribed=true

Retrieve all subscribers to a specific newsletter, from fully registered accounts: 

SELECT * FROM emailAccounts WHERE subscriptions.<NEWSLETTER-NAME>.email.isSubscribed=true AND hasFullAccount=true

Retrieve all subscriptions for an email address: 


Retrieve all users who were created with Lite Registration and are not yet full users: 

 SELECT * FROM emailAccounts WHERE hasLiteAccount=true AND hasFullAccount=false

Webhook Notifications

You can choose to subscribe to webhook notifications for lite interactions, by using version 1.1 or above of Webhooks. The following webhooks may be fired for lite interactions: 

  • account created
  • account updated
  • account deleted
  • account progressed
  • subscription updated

For example, a webhook will be sent in the following scenarios: 

  • Lite account subscribes for the first time > account created, subscription updated (accountType: lite)
  • Existing lite account subscribes to new newsletter > account updated, subscription updated (accountType: lite)
  • Existing lite account unsubscribes from newsletter > account updated, subscription updated (accountType: lite)
  • Existing lite account progresses to full account, requires email verification > account progressed, account updated (accountType: full) (note that in version 1.0 of Webhooks, this would also have sent out an "account created" event)
  • Full account verifies email > account updated, account registered (accountType: full)


Identity Access with Email Accounts

Identity Access, the dashboard for managing your users in Gigya's Console, displays both lite and fully registered users. In the main page, you can view the registration status icon displayed for each user, with "L" for lite and "R" for fully registered: 


In addition, you can use the Status filter to show only users of a certain registration status: 


In the individual user page, under the profile tab,  the indication of the registration status differs between lite and fully registered users:



Lite Registered User

Fully Registered User


Full / Email Account Toggle

For users that have both full and lite registrations associated with their account (i.e. they registered using both the full and lite registration screens), you can toggle between a Full Account view, and an Email Account view. 

The Full Account view displays all the information that is available to the user when they are logged in. Email Account is a merged view that contains all the information available in the full account, plus any information that was saved to this email address during lite sessions. 

For example, a site visitor subscribes to the 'Pets' mailing list with the email, and enters the first name "Vicky", and gives a home address to receive discount coupons. Later, she registers to your site in a full registration process, entering the first name "Victoria", and without providing a home address. In the Full account view in Identity Access, you will see the name "Victoria", you will not see the home address, and you will see the 'Pets' subscriptions. In the Email account view, you will see the name "Victoria" (since it overrode "Vicky", the home address, and the subscription information. 

The reason for this division is that full accounts have a higher degree of accountability, and are not updated automatically by "lite" changes to this account. 


 Information and actions that are associated with the full account, will not be available in the Email Account view.


Importing Lite Accounts

The API used for importing lite accounts is accounts.importLiteAccount. Review the documentation for that API, and prepare a list of the relevant email addresses, and any profile, subscription, or data fields associated with the registrations being imported. Once the information is prepared, you can use IdentitySync, Gigya's tool for data transfers, to perform the import.


Using IdentitySync

If you are using IdentitySync, you can create a dataflow that selects users from the emailAccounts data storage, by using the script and specifying emailAccounts in the from parameter. For a list of supported email service providers (ESPs), see ESP-Marketing Automation-Notification

Click below to see sample dataflows between Gigya and Mailchimp, that implement Lite Registration features.  

 Click here to see an inbound dataflow from Mailchimp to Gigya
 The following dataflow demonstrates importing users from Mailchimp's database, and creating corresponding lite registrations in Gigya's database. You can use Mailchimp documentation to customize this flow as needed.
 { "apiKey": "...", "siteId": ..., "id": "...", "name": "Import lite account from mailchimp", "description": "...", "lastRuntime": "2018-11-07T09:27:17.645Z", "steps": [ { "id": "mailchimp", "type": "", "params": { "apiUrl": "", "apiKey": "...", "listId": "...", "status": "subscribed", "retryIntervalSeconds": 3, "batchSize": 100, "timeout": 120, "maxConnections": 10 }, "next": [ "evaluate" ] }, { "id": "evaluate", "type": "field.evaluate", "params": { "fields": [ { "field": "status", "expression": "status eq 'subscribed' ? true : false" } ], "language": "jexl" }, "next": [ "rename" ] }, { "id": "rename", "type": "field.rename", "params": { "fields": [ { "sourceField": "merge_fields.UID", "targetField": "UID" }, { "sourceField": "email_address", "targetField": "email" }, { "sourceField": "status", "targetField": "data.subscribeToOurNewsletter" } ] }, "next": [ "gigya.generic" ] }, { "id": "gigya.generic", "type": "datasource.write.gigya.generic", "params": { "apiMethod": "accounts.importLiteAccount", "maxConnections": 1, "addResponse": true, "apiParams": [ { "sourceField": "email", "paramName": "email", "value": "" }, { "sourceField": "data", "paramName": "data", "value": "" }, { "sourceField": "UID", "paramName": "UID", "value": "" } ] } } ], "updatedByName": "Admin", "updatedByEmail": "" }
 Click here to see an outbound dataflow from Gigya to Mailchimp
 The following dataflow demonstrates retrieving from Gigya subscriptions to the "Sub1" mailing list, and updating them in the Mailchimp database.


 { "name": "Mailchimp - Outbound", "description": "account > rename > remove > mailchimp", "steps": [ { "id": "account", "type": "", "params": { "deltaField": "created", "excludeEmptyFields": false, "from": "emailAccounts", "maxConcurrency": 1, "select": "*", "where": " = true" }, "next": [ "rename" ] }, { "id": "rename", "type": "field.rename", "params": { "fields": [ { "sourceField": "", "targetField": "EMAIL" }, { "sourceField": "", "targetField": "NEWSLETTER" }, { "sourceField": "profile.firstName", "targetField": "FNAME" }, { "sourceField": "profile.lastName", "targetField": "LNAME" }, { "sourceField": "token", "targetField": "CTOKEN" } ] }, "next": [ "remove" ] }, { "id": "remove", "type": "field.remove", "params": { "fields": [ "profile", "data", "subscriptions", "emai", "token" ] }, "next": [ "evaluate" ] }, { "id": "evaluate", "type": "field.evaluate", "params": { "fields": [ { "expression": "'Subs1'", "field": "SUBID" } ], "language": "jexl" }, "next": [ "mailchimp" ] }, { "id": "mailchimp", "type": "datasource.write.mailchimp", "params": { "apiKey": "...", "apiUrl": "...", "listId": "...", "maxConnections": 10, "newsletterField": "NEWSLETTER", "retryIntervalSeconds": 10 } } ] }
 The dataflows provided in our Mailchimp documentation, rely on the data.subscriptions field and are not an implementation of Lite Registration.


Frequently Asked Questions - FAQ

Expand/Collapse All

 How can Lite Registration help me?

 If your company communicates with customers via email, already offers added value in exchange for an email address, or is considering doing so, you may benefit from Lite Registration.

Manage fully registered users and subscribers in the same place, with a single view of each identity.

Higher acquisition rates: With less fields to fill, a lower level of commitment, and without the need to be fully registered, customers have a better experience and are more willing to subscribe.

Higher registration rates: Building a relationship of trust with customers earlier on increases motivation to register and incentivizes engagement.

Consistent user experience: Similar opt-in screens from newsletter sign up through registration and up to profile management screens.

Information shared by the user initially is preserved and rolled upwards to their user profiles.

Transparency and privacy compliance: all the user information is saved in one place, and controlled by the user - in accordance with GDPR. 

Cleaner data as newest user updates are the ones that are saved.

Prevents deduplication by merging all user data into one email account.

 I already have Gigya RaaS and a full-fledged ESP service. Why should I use Lite Registration?
With RaaS, Gigya provides you with an end-to-end solution for managing customer identities. ESPs specialize in managing mailing lists and subscriptions. Lite Registration ties these ends together and ensures a smooth experience for your users, whether they are logged in to your site or receiving your emails. Lite Registration makes it easier for subscribed users to become fully registered identities, and improves the quality of your user data. Lite Registration includes the following capabilities, which cannot be achieved with a classic ESP:


Data portability and usability: ESPs specialize in email-based newsletters and marketing campaigns. Gigya specializes in managing identities. With Gigya, you can communicate the same subscriber identity to other systems, including POS, CRM and CMS systems. While this is possible with some ESPs, it usually requires a relatively heavy development and maintenance effort. Gigya offers many out of the box integrations with leading systems in the market, and an ETL service, IdentitySync, for building and scheduling consistent custom integrations.

Consolidating all data in one location simplifies the IT structure, rather than trying to render the data from several sources.

More data: Capture all identity information (including likes, preferences, votes, etc.) and not just subscriber information.

Lite Registration streamlines the transition of users from subscribers to fully registered, known identities.

With Gigya, identity information stored with the ESP can be presented to the user in an accessible, friendly way, while also complying with current privacy regulations.

 Does Lite Registration eliminate the need for an ESP?
No, Lite Registration complements your ESP service and does not replace it. You still need ESPs to edit your email content, manage separate mailing lists, create campaigns. Lite Registration ensures that data of your user’s email addresses, names, demographics, preferences etc. is up-to-date and that updates made to that data either in the ESP or Gigya databases is mirrored in the other database, ensuring a smooth user experience and better quality of data. See also the answer to the previous question.
 So when calling setAccountInfo, which account is created: email-based, or full?

Once you have Lite Registration enabled for your account, any setAccountInfo call will create or update the email account. If it involves a registered user, it will also update the full account.

If the call includes a regToken for lite accounts, an emailAccount is also created, or updated if an account already exists for that email.

If the scenario is for creating or updating a fully registered user, then a full account is created (or updated) and the corresponding email account is created (or updated).

 What does a full account contain, that is not included in the email account?
 There are many fields that are part of the full account, which naturally are not included in email accounts, such as loginIDs, and verified, since email accounts also include users who registered with the "lite", passwordless flow. However, you should bear in mind that email accounts may contain subscription information that is more up-to-date than the user's corresponding full account, since they merge both full account and lite registration information. Therefore, when searching specifically for a user's subscription data, we recommend that you rely on the email account's data over the full account data, as the email account may be more up to date if the user has not logged in since editing their subscriptions.

For a full list of the data members included in each account type, see Account REST and Email Accounts Object REST.

 If a user has a full account on my site, and subscribes using Lite Registration, is their full account updated?
 Any customer (whether an occasional site visitor or a fully registered user) can "lite" register as many times as they want. The lite reg screen does not check for existing users and allows everyone to complete the flow with any email. 

After a fully registered user submits a Lite Registration form, a lite registration is recorded in any case. If an email accounts exists for the email address provided by the user, the new information automatically updates the email account. If no email account exists for that email address, a new email account is created. If at a later stage that user logs in and updates their information, their email account is updated accordingly.

See also the terminology section for an explanation of the account types.

 If a user has a full account on my site, and tries to subscribe with Lite Registration, will they receive an error message?
As a rule, only subscription data (saved in the subscriptions object) will be merged into their full accounts, while all data is merged into their email account. However, if the user is currently logged in, it is possible to make an exception, and use the onSubmit event to update their full account.
 How can custom data be stored per lite registration?
There are two ways to store custom data for an email account:

Add a custom "data" field to the lite registration screen.

 This type of data will be stored in the email account, and will not update the fully registered account.

Add lite registration tags.



 Which reports can I use to view Lite Registration data?
 Use the Identity Query Tool and Identity Access to build custom reports.
 If someone registers (full registration) with a subscriber's email address, will they see the user's subscription data?


Subscription data is the only type of data that is merged from the email account into the full account. Because of privacy concerns, the rest of the data (such as preferences, name provided when subscribing, credit card information) will not be exposed to the full account.

 If someone registers (full registration) with a subscriber's email address, will they see the user's personal data?


Because of privacy concerns, personal data (such as preferences, name provided when subscribing, credit card information) will not be exposed to the full account. The only data type that is merged from the email account into the full account is subscriptions.

 When a user subscribes via a lite registration screen, do they have an active session?
 No, only registered users can log in to your site and have an active session.
 Can I collect data for a lite user using progressive profiling?
 No, that type of interaction is possible only for fully registered users.
 Does Lite Registration include a newsletter template, or an email sendout?
No. Most Lite Registration implementations are connected to a third party platform, such as an ESP, which usually handles sending emails to subscribed users and offers its own email templates. Lite Registration is used to sync rich, updated profile information to those third party ESPs.
 Which metadata is stored for a lite registration?

Gigya saves several pieces of information both in the Email Account and in the Subscriptions Object. In addition you can save custom metadata for the account or subscription. These include:

The last time the status of this subscription was changed

Whether or not this email account is associated with a fully registered account

The last time the email account was updated

Custom tags

Custom data

 If the user converts from a lite to a fully registered account, is saved metadata passed on to the registered account?
Lite Registration is based on having both lite and full accounts merged into email accounts. Therefore, the email account stores all the data for that user, whether they are lite or fully registered users. Note that some of the data may be overridden when users perform certain actions. For example, when users change their subscription status, the timestamp that indicates the status of the subscription changes.

When using Lite Registration, the email account is the most updated account, since it gets updated both from full account actions and from Lite Registrations associated with the same email address.


Unable to render {include} The included page could not be found.


Additional Information

For more information, see: 

Customer Identity


UI Builder

Email Accounts Object


Lite Registration Quick Start Guide









  • No labels