FS.setVars not giving proper results
Answered
Hi Team,
Hope you are doing well.
we are using version 1 of full story and implementing the FS.setVars API in one of our pages (page contains two onChange event and we want values like below
FS.setVars('page', {
'market': 'marketName'
});
FS.setVars('page', {
'brand': 'brandName'
});
but we are not seeing this kind of data everytime we change the dropdown value. What is the issue can you please help ? How we can setup it up properly
0
Comments
5 comments
Hi Namit Singh
Welcome to the Community!
With the V1 FS.setVars API, our developer docs explain that the first call must include the
pageName
, further calls can then be made to pass across additional properties. Based on what you have shared above, it sounds like we are not being sent apageName
value to link these properties to a page. Does this sound like it could be the issue?If you still need further help, it will be best to create a ticket to work with our support team, as it sounds like some troubleshooting to look at the Pages / Properties etc in your account may be needed :-)
I hope this was helpful and you have a great day ahead!
Gemma
Hi Gemma Atkins
Thank you for replying. Ok so what you are saying is we shlould use like below
FS.setVars('page', {
‘pageName’: ‘My Page Name’
'market': 'marketName'
});
Like this ?
So if everytime i will change the value from dropdown it will work properly
Hi Namit Singh
Yes, if you provide a
pageName
value we will have something to attach the market / brand etc properties to.If you run into any issues just let us know by raising a support ticket and we will be happy to take a closer look.
Have a good day!
1) FullStory.setVars('page', {
'brand': this.selectedPlan ? this.selectedPlan.displayName:'',
'market': marketName ? marketName[0].displayName : ''
});
2) FullStory.setVars('page', {
'market': marketName ? marketName[0].displayName : ''
});
3) FullStory.setVars("page", {
'market': marketName,
});
Still this is not working fine. Its only giving on load results.
please check below session
https://app.fullstory.com/ui/o-1KH3Y3-na1/session/5495325389762560:(1076057251461139246!4638084450799557755(7001911173970379806(53:53:9474:12403:12403:12404:12419:12419:12419):8573344108684818035(62:62:6483):4088828413662622235(4:4:5):2534905331473856395(3:3:4:5771):7169843707203659136(3:3:3:7916)))
Hello Namit,
Thanks for coming back to us. When you need more general help from the support team, not just community users (such as viewing a session link) it's always best to raise a support ticket.
I know we've been emailing on a ticket today but I wanted to add a note here in case other users come across this thread.
We mention in our developer docs in the limits section for this API:
If the URL host / path do not change as the user navigates sections within your site, Fullstory will not be able to recognise this as a Page change. In this case, customers would typically provide a more generic
pageName
value which must remain consistent but update a property attached to the page name which can be used in search.If there's anything our users in the community can help with, let us know by adding a comment / new post but if you'd like us to look at specific examples in your account, please reply to our email from your support ticket :-)
Please sign in to leave a comment.