You can automatically tag accounts, end users, and features through our javascript integration.
Why is this important?
Tags are an incredibly flexible way to segment your reports at a granular level. Auto tagging provides for deep analysis and insights into your demand data without any manual input.
After a quick setup, you'll be able to view the demand on your product from any customer, user, or product segment.
Tags are completely flexible, so its up to you to decide which tags to implement. Here are just a few examples:
Accounts:
- Location
- Subscription plan
- Contract length
- Company size
Users:
- Persona
- Job role
- Access level
Features:
- Product, module, or instance of the product a request is raised from
- Location of the user who raised the request
- Name / title of the user who raised the request
- Any custom tag based on user data or activity
How to set up auto tagging
If you've already integrated with Receptive, you can just add the new keys for account, user and feature tags in our integration doc to your original integration snippet:
| Key | Description | Example |
|---|---|---|
| account.tags | Account tag categories and their associated tags | Simple: ["automotive", "london"] Tags in categories: [{"location":["london","paris"]}, {"industry":["automotive"]}] Mixed simple and categories: "["automotive", {"location":["london","paris"]}] |
| user.tags |
User tag categories and their associated tags | Simple: ["sales", "london"] Tags in categories: [{"location":["london","paris"]}] Mixed simple and categories: "["sales", {"location":["london","paris"]}] |
| feature.tags | Tags automatically set on features created by the user specified in this snippet | Simple: ["beta", "london"] Tags in categories: [{"area":["sales","stock"]}] Mixed simple and categories: "["beta", {"area":["sales","stock"]}] |
| user.allowed_products | Products that user is permitted to view |
[{"name" => 'Receptive', "id" => 'external_id'}, {"name" => 'Product A', "id" => 'Product A'}] Where external_id is the existing or new product identifier. Read more here. |
If you integrated before 1st Jan 2017, and you have "secure mode" switched on, (so you sign the snippet data), you'll need to update the signing method to use JWT signing. This should be simpler to develop than our earlier manual signing method.
If you haven't integrated with Receptive yet, just follow the steps here.
Any questions? Email support@receptive.io or use the form here.
0 Comments