-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
chore(PPDSC-2234): investigate Storybook analytics #338
Conversation
You can preview these changes on: |
}; | ||
|
||
if (window && window.tealiumTrack) { | ||
console.log('SEND_EVENT', event); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left over console log?
if (window && window.tealiumTrack) { | ||
console.log('SEND_EVENT', event); | ||
window.tealiumTrack(event); | ||
// window.utag.view(e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leftover comment
}, | ||
consent: { | ||
accountId: 259, | ||
//TODO: change to https://storybook.newskit.co.uk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left todo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, except the comments from Marco.
}; | ||
|
||
addons.register(ADDON_ID, api => { | ||
// The addon only sets the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incomplete comment
// send initial page view event, since storybook doesn't do it via STORY_CHANGED | ||
// When the preview boots, the first story is chosen via a selection specifier | ||
api.on(STORY_SPECIFIED, () => { | ||
console.log('STORY_SPECIFIED'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the console logs?
* chore(PPDSC-2234): investigate Storybook analytics * chore(PPDSC-2234): change addon * chore(PPDSC-2234): change tracking function * chore(PPDSC-2234): use newskit components * chore(PPDSC-2234): update storybook and plugins * chore(PPDSC-2234): configure source point * chore(PPDSC-2234): update snapshots * chore(PPDSC-2234): update storybook * chore(PPDSC-2234): update label * chore(PPDSC-2234): config tealium profilleid * chore(PPDSC-2234): enable tracking * chore(PPDSC-2234): add page name * chore(PPDSC-2234): fix fonts paths * chore(PPDSC-2234): fix deps * chore(PPDSC-2234): fix undefined error * chore(PPDSC-2234): fix js error * chore(PPDSC-2234): fix object * chore(PPDSC-2234): adress comments * chore(PPDSC-2234): update privacy policy link
PPDSC-2234
What
2.1. Created a storybook plugin which utilises our Tealium and Consent component so we can track
2.2. Fixed Tealium component to take reactHelmet prop as its described in the docs.
I have done:
I have tested manually:
Before:
After:
Who should review this PR:
How to test: