Lookup variable and stiching user together

1

I am running into a problem i seem to cannot solve myself…

If I receive a webhook on the server and store the event data in a database (stape store) while using the lookup variable, it only works for the store writer tag, but not for my other events. Is it because I’m missing a way to link it to the specific user? I thought a cookie could solve this, but it doesn’t seem to work when I try to set the cookie using CookieMonster with the webhook trigger to set the cookie. Hmm, do you have any tips? :smile: I’m a bit stuck here.

2

You can’t set a cookie in response to webhook. Webhooks are sent by the servers, not browsers.

Yes, seems this is before you lack a common datapoint to stitch the two things

3

That makes sense! But do you have a recommendation for a common datapoint to stitch the things toghter`?

4

Any common value would do. I don’t know your events and payloads. Figure out what’ common in webhook and other events - use that.

5

Yes i dont think there is anything …

This is payload from the webhook:
{
“email”: “{{ person.email }}”,
“first_name”: “{{ person.first_name|default:‘’ }}”,
“last_name”: “{{ person.last_name|default:‘’ }}”,
“phone_number”: “{{ person.phone_number|default:‘’ }}”,
“country”: “{{ person.Country|default:‘’ }}”,
“region”: “{{ person.Region|default:‘’ }}”,
“city”: “{{ person.Country|default:‘’ }}”,
“email_marketing_consent”: “{{ person|lookup:‘Accepts Marketing’|default:‘’ }}”
}

I dont have any of that in like a view item event (using Stape’s datalayer)

This seems like it would require some kind of development then? or is there a tag or something that do it? What do you suggest from here.

6

again, you need to have something in common, otherwise there’s nothing to stitch.

your webhooks needs to have something that is available on the browser (cookie values for instance). There’s no single solution here, I don’t even know what your webhooks are to be able to suggest anything

7

Alright. Its a webhook from Klaviyo that gets send to the server when we get a new lead. I will then store the event data from the klaviyo webhook in stape store

8

You get that lead from an online form submission I assume? If so, what’s the point of handling it via webhook? Track form submission, store data from there, this will be in a browser env so you can throw any kind of cookie on the customer like just that set user data directly for instance.

9

Yes thats actually what i do already and it does work.

But lets say theres running a lead ad on Meta, where you signup to the newsletter directly on Meta, and dont go to the website.

In that case it woudnt work - but mabye i am overthinking it. Leads directly from Meta tends to be worse quality anyways