Franz92

Thank you, that’s very good to know. Maybe the author can work with the Succuri team.

Hi,

I’m afraid we’re still experiencing problems here.

Neither did we change the SALT keys manually, nor can Succuri do that.

Other plugins keep the password (but can’t encrypt it), whereas for us it’s empty. Don’t know if this is relevant. Or this.

What else could cause the password to be invalidated?

It always happens on the weekend.

Could

• plugin conflicts,
• configuration issues in wp-config,
• server-side caching issues,
• database issues or
• updates to WordPress / FluentSMTP or unrelated plugins

cause this problem?

Best,

Franz

Hi,

thank you for your reply. That’s odd. Neither did we change the SALT keys manually, nor can Succuri do that.

Other plugins keep the password (but can’t encrypt it), whereas for us it’s empty. Don’t know if this is relevant. Or this.

What else could cause the password to be invalidated?

It always happens on the weekend.

Could

• plugin conflicts,
• configuration issues in wp-config,
• server-side caching issues,
• database issues or
• updates to WordPress / FluentSMTP or unrelated plugins

cause this problem?

Best,

Franz

Hi Amimul,

We’re using a direct connection to our?SMTP?server.

The issue happened again. Please advise as to how we can fix this. 

Thanks.?

Best Regards, Franz.

Hi,

just chiming in that I’ve created a feature request for adding [unit_pricing_measure] to the feed in here:

https://woocommerce.com/de-de/feature-requests/google-listings-and-ads/

If they don’t add this functionality, we might have to switch to the plugin offered by Adtribes.io

Best,

Franz

Wollte ich gestern, da kommt die “Passwort vergessen” Mail leider nicht an, weder bei mir noch beim Kunden. ??

Da das Problem ja doch recht kritisch ist, meldete ich mich hier.

Das hei?t aber, dass das kein bekannter Bug ist?

• This reply was modified 1 year, 1 month ago by Franz92.

Hi! Having trouble reaching you again via the priority support, tried both email adresses. Could you take a look, please?

Just did, thank you!

Hi,

ah, cool. Thank you! Okay, it seems that’s true. But I guess I’ll have to somehow weave in the cookies so that I can use the integration?

No, I checked. Polylang Pro may be your best alternative.

Silly me: Issue 2 is solved by forcing users to allow, deny or customize their settings upon opening the page.

Then everything works. Thanks!

Ah, 1 was easy: We just use RegEx to match for either deny or undefinied.

That way the exception only does not fire when the user allows tracking.

Screenshot: https://pasteboard.co/2PUzAiT879qz.png

But issue 2) persists… and I am at a loss on how to solve that. ??

PS: I just understood that you did not create new triggers for “Statistics is false” above, but just added a filter to the existing triggers which trigger the eCommerce tags. Silly me. (But that doesn’t solve for 2).) : )

Hi Aert,
thank you so much, I implemented that. And yes, you are right: Trigger groups are very buggy, as they don’t carry over consent.

A pointer for further readers.

I created a variable ‘1st party cookie’ with cookie name ‘cmplz_statistics’. Then added a custom event with this variable on ‘deny’ and added it as exception to the event tag named: “Statistics” is false.

He added a trigger based on a custom event: https://pasteboard.co/RTXIx02sj2eO.png (Hower, instead of “false” it must say “deny”.

And this is the configuration of the variable: https://pasteboard.co/XpGuHOwUaxBs.png

It mostly works. However, there are a few issues.

1. Tracking happens before a selection (deny or allow) has been made by the user in the Complianz pop-up – when the user has not allowed or denied yet, the exception in the tags will not fire. Thus we have to wait until after the complianz event has been fired on the page, but the gtm4wp events are fired before.
2. The blocking triggers fire only on the cmplz_event_statistics, but not on the Google Analytics eCommerce events. We’d actually need to get the value of the first party variable into the exception.

I will ponder those two questions! ??

That’s my debug link in case it helps.

Thank you! That worked perfectly.

Hi!
My return for the 1st party cookie variable upon the orderComplete event is:

"{\"consents\":{\"essential\":[\"borlabs-cookie\",\"google-tag-manage" +
"r\",\"woocommerce\"],\"statistics\":[\"google-analytics\",\"hotjar\"" +
"],\"marketing\":[\"facebook-pixel\",\"klaviyo\"]},\"domainPath\":\"b" +
"engelmann.com/\",\"expires\":\"Tue, 04 Apr 2023 13:34:37 GMT\",\"uid" +
"\":\"xftc0mgc-xg1rydxy-mrco30ac-rgzb7yd1\",\"version\":\"4\"}"

For “Google Analytics Consent Status” upon the orderComplete event it is

true

I’ve used this for testing.

> What we could do is to test if we read the Borlabs consent cookie directly, does this give better data collection quality? If yes, I could contact them to propose a change in their variable template.

Does that help?

Coverage seems to be a lot better. It was 29% before, 51% now. (Still lower than what I am seeing on other sites, but a least better.)