Skip to main content

How do I go live with self-service 2.0

NOTE if you only want a preview of the setup before going live, go to the guide How do I test the new self-service.

Once you have all the settings as you want them, you must

  1. Open the account menu

  2. Select Primary settings → scroll down to the customer service section and click the Edit customer service settings button

  3. Scroll down to the new self-service section

  4. Change Self-service Version from version 1 to version 2 and click Save

Technical

What specifically do our web developers need to change to point to v2.0? Should iframe-src, script-src (iteras.js) or other references be updated? Is there a migration guide we can follow?

The new self-service is embedded in exactly the same way. The only difference is that when we have the new custom domains ready, a different URL must be used for our plugin. Read more about this in the guide Own domain for self-service and forms.

Does v2.0 change the HTML structure and class names compared to v1? Our CSS customizations depend on the class names mentioned above – will they still work, or do they need to be rewritten for the new structure?

A lot has been changed in the HTML structure. However, it is only the self-service in this round, i.e. all purchase flow pages remain the same. The styling system is completely different in the new self-service, so the way the appearance is changed should not require you to migrate code over to v2, but you should probably review the customizations you have made and see whether things look as they should in the new one. There are more details about styling the self-service here: https://app.iteras.dk/api/docs/js/theming/

And you can change the texts under "Page content setup" on the business policy.

If there are any code customizations you want to bring over to the new self-service, there is a new code customization field exclusively for the self-service in the customer service configuration.

Tracking

Tracking works in the same way as the old self-service. We have a policy of not tracking users, so there is no need for cookie pop-ups when using our components, but you are very welcome to track and manage consent. This is done in the same way as the order process, by writing some JavaScript code that calls Iteras.track() for what you want to track. It is also possible to embed tracking systems directly in the self-service. Here it is again important that you have consent under control.

Did this answer your question?