Picture of Iframe | Customer Mapping

Iframe | Customer Mapping

NOTE: The customer you are using in Infigo must be a REGISTERED user (with the customer role: 'Registered').

The customer GUID is required, and when you are mapping customers from your external system to Infigo, you can choose to map the Infigo customer ID, email address, or customer GUID. The first two are readily available in the UI, and the email address should generally match anyway. However, the customer GUID, which is necessary for subsequent API calls, requires an API request to return it.

Depending on how you intend to implement this integration, you can either:

  • Ensure that all your customers in your external site have a corresponding customer created in Infigo (this usually works well in a fixed B2B scenario).

  • Use one 'website' user in your system that is always passed to create the editor and place the orders.

Important: Ensure all jobs from one order are linked to a single customer; otherwise, the Create Order call will fail.

In either case, the customer being used needs to have a mapping entry in Infigo that can be sent with the requests. If you don't store the customer GUID, then the following API call is required:

Endpoint:

Get Customer by Id

The id can be the Infigo customer ID, the customer email address, or the customer GUID.

The response to this request contains a variety of customer data, from which we need to capture the "Guid" (responseJSON.Guid).

Customer Guid

If you don't have a customer linkage in your system, you can call the Get Customer SSO Url. This will automatically create a customer in Infigo with the provided GUID if the customer is not found. If the customer already exists in Infigo, this call will simply try to generate a new SSO URL for the customer.

Incomplete
Migrate Customers Data

In the scenario where an e-commerce platform supports guest users, the following steps need to be considered for migrating customer data seamlessly:

  1. Initial Interaction:

    • Users open the website as non-authenticated visitors.

    • They browse products and may access an iframe for editing or customization.

  2. Add to Basket:

    • Users add items to the basket while still in a non-authenticated state.

  3. Login Process:

    • Users proceed to login to their accounts.

    • Upon login, depending on the e-commerce platform's functionality, basket items are typically migrated to the logged-in customer's account.

  4. Handling Infigo Jobs:

    • Infigo has a design limitation where orders cannot have job owners from different users.

    • When users were guests (non-authenticated), they might not have had an email associated with their basket items.

    • To handle this in Infigo, a new user may need to be created with a random GUID to represent the non-authenticated user.

    • Once users log in, they already have a user in the e-commerce platform, and a call needs to be made to Infigo to migrate jobs to the new user's account.

    • If migrating jobs at the login stage is not feasible, it can be done before placing the order in Infigo.

This process ensures that users' basket items and associated job data are seamlessly transferred between the non-authenticated and authenticated states, maintaining consistency and preserving user data integrity.