Skip to content

Update AJS FAQs to include adding new context fields #4102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 24, 2023
Merged

Update AJS FAQs to include adding new context fields #4102

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c940402
Update AJS FAQs to include adding new context fields
ashton-huxtable Jan 23, 2023
3828114
Include note that custom context may not be forwarded to destinations
ashton-huxtable Jan 23, 2023
c19d095
Apply suggestions from code review
Jan 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,25 @@ analytics.track("Receipt Viewed", {}, {

This works for any [context field](/docs/connections/spec/common/#context) that Segment automatically collects.

### Can I add context fields that do not already exist?

Yes. Similar to overwriting context, you can add context fields by passing them into the options object as the third argument of the event call. For example, the analytics.js library does not automatically collect location information. To add this into the context object, pass it into the third argument as in the example below:

```js
analytics.track("Order Completed", {}, {
location: {
latitude: '39.7392',
longitude: '104.9903'
}
})
```

> info ""
> You must pass the context object with the call, event if it's empty, as shown by the empty object in the example above.

Some destinations accept properties only. As a result, custom context fields you add may not forward to these destinations.


## Known issues:

[Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues)