Skyscanner truncates and then hashes / one-way-encrypts the PNR as soon as we receive it. We do not store or log the original PNR / bookingReference anywhere through the SAT data pipeline - it gets hashed as soon as we receive it.
Articles in this section
- What do you need to do to install the SAT solution?
- How many days is your look back window for attribution purposes in your platform?
- Who is performing the processing of the (encrypted) PNR or booking reference number?
- For what purposes is that data processed?
- Does the tag need to only fire for Skyscanner traffic?
- How do I fire the tag only for Skyscanner traffic?
- Where can I find documentation?
- How is this solution different from old tracking pixel, keyword tracking?
- Can I delete my old pixel now?