Sendlane in v10.10

[lesliekirk]

The documentation for the version of Sendlane which is included in v10.10 mentions

Beacon JavaScript – This gets output on all pages and should now be edited.

But I can't find what is supposed to be edited.
https://docs.miva.com/miva10/referen...on#miva-config

It also mentions Adding Forms to Miva and that

Miva makes it incredibly simple to add custom forms

Where is this magic button in Miva? I was able to stumble around and find where the Forms creation resides at Sendlane.

FYI - I found the installation of the Sendlane module (pre v10.10) easier...

[Nick]

lesliekirk There is no need to edit any template code for the new Version10.10.00 Sendlane module. When the module is installed there are two JS resources added to the working branch in the store.

sendlane_beacon is added as module type resource so it can not be edited. It is important to mention that the module type resources are added to the head item with the modules parameter, ie <mvt:item name="head" param="modules" />. So make sure that item is located within the head tag.

sendlane_events is added as an inline script so that you can add additional tracking events if needed. It comes with product_viewed, added_to_cart, and checkout_started

The new Sendlane forms section of admin is used to copy the script provided by Sendlane when creating a form in Sendlane. So you would go in Sendlane and create a new form, then add the provided code to the Sendlane forms section of Miva. The module will then add the necessary code for the form to work correctly.

It should be a pretty straightforward integration with little to no setup aside adding credentials and adding in Sendlane forms.

[lesliekirk]

lesliekirk T

The new Sendlane forms section of admin is used to copy the script provided by Sendlane when creating a form in Sendlane. So you would go in Sendlane and create a new form, then add the provided code to the Sendlane forms section of Miva. The module will then add the necessary code for the form to work correctly.

That was the part I guess wasn't clear to me - Sendland Forms in the Miva Admin.

So where do these forms get placed? I just need to replace a previous sign up form with the one from Sendlane.

[Brennan]

These forms are typically popup forms that overlay the site. You set in Sendlane which URLs you want them to show up on.

For someting like a global newsletter signup box in the footer, you could need to manually place the JS code generated by Sendlane at the location in the Global Footer where you want the newsletter signup box to show.

Sendlane calls these inline forms, and they will give you a div which you can replace in the location your newsletter signup box is today,

Example:

<div class="sendlane-form" data-form-key="eyJkb21haW4iOiJtaXZhNCIsImZvcm1faWQiOiIxMjIzM TRhYS0wOGYwLTQ4YTMtYmYwYS03N2E3ZDViZGUxNmUifQ=="></div>

[lesliekirk]

Thanks, Brennan - yes I'm working with the inline "template" for Sendlane.

Just a suggestion - like I said, the docs from Sendlane for the installation using the module from the app store were very very well-documented but you might want to reach out to Sendlane and have them pull all of what they have (even though it was super easy and Miva specific).

[lesliekirk]

Next question Brennan - how do you add the subscribe checkbox at checkout? Can this set of instructions still be used?

Once the checkbox is checked, navigate to your Miva store's OCST file via User Interface > Templates > OCST

Add the following snippet anywhere you'd like the checkbox to display before the </body> tag

<div id="update-record"> <input type="checkbox" name="sendlane_accepts_marketing" value="Yes" checked /> Accept Marketing Emails </div>

From this page: https://help.sendlane.com/article/34...a-and-sendlane

[Brennan]

The checkbox during checkout not supported in this initial release but it will be added in a future version.

[lesliekirk]

The checkbox during checkout not supported in this initial release but it will be added in a future version.

Thanks, I will let the storeowner know.

[lesliekirk]

lesliekirk There is no need to edit any template code for the new Version10.10.00 Sendlane module. When the module is installed there are two JS resources added to the working branch in the store.

sendlane_beacon is added as module type resource so it can not be edited. It is important to mention that the module type resources are added to the head item with the modules parameter, ie <mvt:item name="head" param="modules" />. So make sure that item is located within the head tag.

sendlane_events is added as an inline script so that you can add additional tracking events if needed. It comes with product_viewed, added_to_cart, and checkout_started

The new Sendlane forms section of admin is used to copy the script provided by Sendlane when creating a form in Sendlane. So you would go in Sendlane and create a new form, then add the provided code to the Sendlane forms section of Miva. The module will then add the necessary code for the form to work correctly.

It should be a pretty straightforward integration with little to no setup aside adding credentials and adding in Sendlane forms.

Hi Nick - point of clarification. When you say

to no setup aside adding credentials

which credentials are you referring to?

The store owner has been told by Sendlane:

I contacted sendlane, and they are saying we are not sending events to sendlane. Can you check this for me please?


“I found a Sendlane beacon code installed on your website but unable to see the correct event_id of beacon “

Mainly 2 points to check (1) Installing your Sendlane account's Beacon to your website (2) creating Event tracking ( as you have custom store integration, for Shopify and other popular platforms all events are inbuilt with platforms )

Let me share with you some details to make it easy.
Here is the Guide to install Beacon to your website > https://help.sendlane.com/article/72-beacon

I had previously asked about

I have followed these instructions and have previously asked about this in the instructions:

Beacon JavaScript – This gets output on all pages and should now be edited.

It sounds like it DOES need to be edited and yes I have checked on more than one occasion to verify the <mvt:item name="head" param="modules" /> is in place.

[Nick]

lesliekirk the docs page is a typo and has been updated to say "should not be editied"

As for the issue you are seeing please submit a ticket to our support team and we can take a further look as to why the event_id is not available.

[lesliekirk]

Thanks Nick - I'm getting the ticket submitted.