> * Security vulnerabilities and how Northpass security team approaches them in relation to having Northpass platform under Pipedrive domain (learn.pipedrive.com)
> * Cookies that should be included in OneTrust, user preference to be respected. We have had a conversation with Norm around this but want to confirm we’re all good
> * Deletion of data - how is this working on the Northpass side (for user account created for learn.pipedrive.com). Northpass has already confirmed it’s possible but we need to document how
> *Data Meeting*
> * Understand what Northpass-Segment integration does out-of-the-box. From there establish if there are any gaps and if so how we can bridge them.
> * Find out what data we could bring to Pipedrive DW from Northpass native tracking and how. Things like course stats and other learning XP related items.
> * Establish what role information we pass through our SSO plays in data flows.
Lukasz: we don't have those events, but we can try to build them. Since this is a customized school, events are not being tracked as much. We may be able to pass this information.
Norm: What is the tracking unique identifier? Session ID? User ID?
> Pipedrive will create the unique ID, or passing in a pipedrive owned identifier that can be passed to segment. They will have to define what attributes and data points that they will want in the warehouse. To add, Segment can track when there is no clear user identification. Segment has a mechanism of "anonymous ID" and try to persist it in the cookie. They can use this for non-known users.
For Northpass, most of the time, users will have identifiers. If they come from Pipedrive - they will have the Pipedrive ID. If from Northpass, our UUID will be passed. We need to ensure that param is passed. This would be ideal instead of trying to rely on the anonymous ID.
Some clarification from Bjorn: are we discussing a scenario of segment tracking within all Northpass web content? Right now, design is fully under Northpass control. This makes them a little less confident, because they want to make sure it is totally trackable.
Third point: There is some native tracking. Is there a point at building everything up via Segment? Such as Course Completion, are these being passed via events? We have some webhooks, but what do they mean by "events"?
* Can OneTrust share consent snippet across pages? Main snippet is from Pipedrive.com, but it would carry over to other sites from the source snippet.
* Will we know who *hasn't* given OneTrust consent? We could create a boolean prop to show who has or hasn't given consent.
* Are they/can they tie this into Consent and Privacy Policies as dictated by Pipedrive? Good question (Kaisa) and this will need to be brought up in their meeting next week.
* Would it be possible (or are they considering) to extend their Cookie Banner into Northpass? Yes, they are.
What are the options to get the data out of Northpass and into their warehouse?
DONE: Bjorn our data schema. Send him our 3-4 options in an email so he can read through the options. The options I provided were Encrypted Dump into S3 bucket (Flink), Secure Data Transfer, Webhooks (not ideal), and Snowflake/Look for customers who are also on Snowflake or Looker.
redirected to B > Browser sees it’s a 301 redirection so it adds this redirect to cache > We change in NP from
A->B to A->C > User visits A > User was redirected to B (because his browser has this redirect in cache).
The only way to fix it it’s a requesting the user to clean cache in his browser. So if the user is unauthorized and goes
to app/courses, we will redirect him to sign_in page with 301. The browser will cache sign_in page, and the userwill be automatically redirected to sign_in page when the user tries visit app/courses. This will cause a loop.
301 makes sense if the website they are accessing was permanently moved to other location. In this case they are trying to access courses list but are redirected to sign in page because they have to be authenticated before they can access it. If we redirected them from courses to sign in page with 301 the user’s browser would save the redirect location (sign in page) and whenever the user tried to access courses web page their browser would move them automatically to sign in page making courses page inaccessible for the user. The only way out of it is cleaning browsers cache. However once they cleared the cache they would remove the cookies as well. The cookies keep the information about users identity. This is helpful because with that they don’t have to log in each time they visit our platform. But once the cookies are removed they would be again redirected to sign in page keeping them in this vicious circle.The reason to use 301 is to tell the browser “forget about this old location of the page you are accessing, this page is now here, also store this location and use it whenever you try to access this old location”.
Only the title can be clicked when search results are returned. We need to be able to click the icon or description as well Not a problem - will get this started ASAP
Last year they were already window shopping for LMS. Ines watched a demo of Northpass.
## 08/01/2023
### Ongoing Issues
Localization:
* Can we just launch a single language? No. They want to launch all languages.
* This will affect renewal - if we can't do localization, then they won't renew.
* James - throwing it out there: this is just the tip of the iceberg for localization. They will only be adding more content and languages as time goes on.
* James: can we do one instance per language? Norm: yes, but each instance would have a different sub-domain.
* Ben: Not ideal they want a `learn.pipedrive.com/en` or `/de`.
SEO:
* Dynamic rendering? Ben has some ideas to share with me.
* Language picker was visible for several days, which got picked up by Google.
* Check again in a day or two to see if its not picked up.
* Confusion on the language codes.
* Any timeline for adding language codes to URLS of courses (`/app/courses`)
Other:
* Customize the welcome email.
* Workflows for a welcome email?
Will joined late - nothing new to add.
Final item from James:
* Is there anyway to get one more contact into our Slack channel? Especially an SE engineer.
* The support experience "wasn't great" when going via Support because they were not aware of the customization.
* He would like comments in the Sheet ASAP for all the high priority items.
Kat: if localization is fixed will that secure the renewal? Yes, James believes so.
