My website deployment is not triggered or has triggering errors

You've taken great care in creating your campaign and diffusion, but things aren't working as planned?

Don't worry! We have identified some possible solutions here, in order to quickly resolve the situation.

The elements below allow you to easily identify the blocking points that could explain why your button, popin, bar, etc. does not appear on your site.

  1. Is the tag well set on the domain?
  2. Is the defined domain really the one declared in MyFeelBack?
  3. Is the diffusion associated with the right domain?
  4. Are the conditions based on the URL path correctly configured?
  5. Are the variables or attributes used for your diffusion valued in the tag?
  6. Do the solicitation criteria allow me to trigger the delivery?
  7. Is the tag implemented as part of a Single Page Application (SPA)?

1. Is the tag correctly placed on the site?

To check that the tag is correctly fitted, consult the console.

Once you have accessed the Console, type _Mfb_domain next to the blue arrow. Press enter

Here, you must have the domain, configured in MyFeelBack and associated with the tag, which is displayed (Cf picture).
If the error below is displayed, it means that the tag is not placed or not correctly placed on this page.

Sometimes the tag is not triggered until the cookies have been accepted: remember to check with your teams to see if rules of this type are in place.

Read the following article: How do I implement the Trigger Tag on my site?

2. Does the domain of my site correspond to the one declared in MFB?

Once you have checked in the console that the tag is present, we invite you to check that the domain name associated with the registered tag is compatible with the one used by your website.

As a reminder, the domain of your website must cover the domain declared in MyFeelBack.

  • To cover all the sub-domains used on your site, enter your generic domain without the sub-domains: .monsite.com
  • To restrict to a sub-domain or main domain only, enter exactly the name of the target domain or sub-domain: www.monsite.com or monsite.com for example.

To check, go to the console and type _Mfb_domain next to the blue arrow. Press enter. Then type document.domain and press enter.

If your document.domain differs or if "_Mfb_domain" is more precise than "document.domain", it means that the domain associated with the registered tag is not compatible with the domain of your site. In this case, we invite you to update the domain in MyFeelBack or to integrate the right tag.

For example if the document.domain displays http://espaceclient.mybrand.com/ the _Mfb_domain must display espaceclient.mybrand.com OR .mybrand.com

To see the domain declared in MyFeelBack, go to the "Settings" section, then select "Deployments" and finally "Domains".

Capture d’écran 2021-03-02 à 09.28.12

3. Is the deployment associated with the right field?

With the multi-brand option, you can deploy on several domains at once. Check in your diffusion that the diffusion is associated with the domain on which you wish to perform the triggering.

Capture d’écran 2021-03-02 à 09.40.23

4. Are the conditions based on the URL path correctly set up?

The URL Path is everything that follows your domain name without the parameters and anchors. 

Exemple : https://mywebsite.com/my-path-url?settings#anchors

Your "On Page" or "Page Visited" conditions must therefore not contain any domain, anchors or parameters.

We also invite you to check :

  • The case ;
  • The presence of space ;
  • The selected operator.

5. Are the variables or attributes used for your diffusion valued in the tag?

If conditions are based on a variable or attribute, check in the console that the values go back to the tag : _Mfb_ud

We also invite you to check in the conditions :

  • The scrapyard ;
  • The presence of space ;
  • The selected operator.

6. Do the solicitation criteria allow me to trigger the diffusion?

Conditions of use

If a solicitation condition is in place, consider testing it in private browsing :

Triggered once per visit

By default, each broadcast is triggered once per visit to the site.

If you want the button or bar to reappear each time the conditions are met, remember to uncheck this option. Attention, this is not recommended in the case of a popin.

7. Is the tag implemented as part of a Single Page Application (SPA)?

In the case where the triggering is planned on a website or part of a website of the Single Page Application type, the integration of the tag is specific.

You will find the integration instructions specific to a SPA in the "Settings" section by clicking on "Broadcasts", then "Trigger tag" and "Installation on a Single Page Application (SPA)".

Read the following article: How do I implement the Trigger Tag on my site?

Want to try? Click here