As a user, I want to see that LG has Student offers while I'm browsing a specific product, click on it, get verified and get redirected to the same product in the Students Store.
We can achieve this the same way Samsung is doing it, via the On-Site Messaging product from Gocertify. Take a look at this video to understand the general journey.
Before jumping into details, let's review the current integration, step by step:
- Shopper visits https://www.lg.com/uk/shop/for-keyworker/
- Shopper clicks on "Verify Now" CTA
- Shopper is redirected to https://secure.gocertify.me/at/lg/key-worker
- Shopper completes the verification
- Shopper clicks on final Gocertify CTA button
- Shopper is redirected to Partnerize (with a destination parameter set to
/uk/partnersand authentication parameters) - Partnerize redirects the user to that destination url (back to LG.com)
- At
/uk/partnersthe shopper is authenticated and redirected to (with JS): - Partnerize cookies are set properly at LG.com (see that
clickref=1101|DgmzU6Iparameter)
Recommendation to improve analytics: Remove the
utmparameters in Partnerize, so Sessions are not mixed up in Google Analytics or other provider
This banner will be loaded only in certain products. LG will have access to Gocertify's dashboard and upload a list of all the SKU's that should display the banner.
This integration requires 2 little changes to existing integration:
- Add a new component wherever the banner should appear
- Update the
/uk/partnerspage to do a final (and optional) redirect
First, we need to make sure the gocertify.js script is loaded in every Product page.
Then, in the product page template, we need to add this line of code wherever you want to load the new banner (remember that it won't be loaded every time, only for the SKUs specified in the Gocertify dashboard):
<gocertify-target identifier="{{ the SKU of the product }}"></gocertify-target>Once the shopper finishes their verification in Gocertify, they are currently landing in this page:
Now, there will be a new extra parameter called pdp that will contain the path where the user should be redirected after the authentication process being done using the clicktimestamp + signedtoken + signature parameters. For example:
Note that pdp=%2Fmonitors%2Fgaming%2F45gx950a-b%2Fbuy.
The user should now be redirected to:
It's super important that the clickref parameter stays in that final redirect. All the other parameters are optional.
Remember that there will be cases where that pdp parameter is not present (or empty). This happens when the user didn't start their journey from a specific product page, and did it from the Students page instead.
- Shopper visits this gaming monitor (public website): https://www.lg.com/uk**/monitors/gaming/45gx950a-b/buy/**
- Shopper sees the banner for "Exclusive discounts for Students" (for example)
- A popup opens and user starts their verification process
- Shopper clicks on final Gocertify CTA button
- Shopper is redirected to Partnerize (with a similar parameter than before, but also some identification of the current product):
- Partnerize redirects the user to that destination url (back to LG.com) [This redirection will be discussed below]
- Shopper lands in the same gaming monitor in the partners portal: