FullStory APIs to track who Viewed Ad, and Clicked an Ad

New
Avatar
ritwik.dutta

We are currently using FullStory EventFilters to track metrics on how many users 

a) Viewed an Ad

b) Clicked on an Ad

c) And then pressed the Buy Button on the Next page, after clicking the Ad.

Currently, we are exceeding our Company License Usage Limit. The Event Filters stop tracking data, after the third week in a month. Our alternative is to use the various APIs to track views, and clicks on an Ad.

I am trying to figure out which option would be the most suitable to conduct this. I am thinking Browser API, is the best option.

https://developer.fullstory.com/browser/capture-events/analytics-events/

1) Would webhooks be a better option? also, I believe ServerAPI would not be a suitable method, since we are tracking what is occurring in Chrome.

https://developer.fullstory.com/webhooks/getting-started/

https://developer.fullstory.com/server/v1/users/set-user-events/

2) Additionally, given we exceeded the usage limit on EventFilters, would APIs still function as backup, or they also part of that usage limit?

0

Comments

3 comments

  • Avatar
    Lindsay Zubrickas

    Hey @MarkAlex45! Thanks so much for your question! 😊

    I would first need to clarify what type of use limit you are referring to before provide the best solution, but here are some options that should help point you in the right direction:

    1. Session Limit: If you’ve exceed your contractual session limit, your best bet would be to look into our Session Overages feature. This gives you a temporary option to continue capturing FullStory sessions and product analytics data in the event that your session volumes ever surpass your contractual session limit. Since these limits are specifically for APIs, you would not be able to use the API options listed as an alternative. You can read more on our limits here. Webhooks are outbound, so it wouldn’t provide you with the solution you are looking to achieve with API’s. 
    2. Watched Element Rate Limit: If the limit you’re referring to is your Watched Element Rate Limit, this is often caused by choosing a selector that is too broad, matches too many elements on the page, or gets removed and added to the DOM repeatedly. I would suggest auditing your Watched Element selector rules to make sure they are as precise as possible. You could try to implement a custom event as an alternative to a watched element but you would want to be mindful of Property Rate Limits. 

    Please don’t hesitate to reach out should you have any further questions! 

     

    0
  • Avatar
    ritwik.dutta

    Thanks,

    What I’m mostly curious about is whether the event API counts toward the session limit. And specifically, will it work after we hit our session limit?

    0
  • Avatar
    Lindsay Zubrickas

    Hey @MarkAlex45! Thanks so much for following up with that information! 

    To answer your question, yes, the event API does count toward the session limit. For FS.event, the burst limit is 10 calls per second and the sustained limit is 30 calls per minute. If these limits are exceeded for a given time interval, subsequent Client API calls within that time interval will not be captured in FullStory. You can read more on that here. 

    Please let me know if you have anymore questions! 

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post