At a Glance
- Tasks: Support the migration to Snowplow Unified and modernise web analytics.
- Company: Join a forward-thinking team focused on data innovation.
- Benefits: Flexible working hours and the chance to work on exciting projects.
- Other info: Collaborate with analysts and engineers in a dynamic environment.
- Why this job: Make a real impact by enhancing analytics capabilities and user tracking.
- Qualifications: 5+ years in Analytics Engineering with Snowplow experience.
The predicted salary is between 50000 - 65000 £ per year.
Contract Snowplow Migration Support Overview We're looking for an experienced Analytics Engineer or specialist consultancy to help complete a migration to the Snowplow Unified package and modernise an existing web analytics stack built on Snowflake and dbt.
Project Scope The current implementation is partially migrated, with a mix of native Snowplow Unified models and legacy custom-built solutions.
Key objectives are: Complete the Snowplow Unified migration Move deprecated and custom models onto native Unified outputs Upgrade to a current package version Remove unused components and validate metric parity with legacy reporting Implement user stitching Configure user identity resolution and mapping Enable customer-level journey tracking using a provided master identifier Migrate to the Snowplow Attribution package Replace existing custom attribution models Configure required dependencies, including the Conversions module Engagement The consultant will work closely with analysts and data engineers, embedding within an established dbt workflow and review process.
The engagement is expected to be up to 5 days per week, though part-time arrangements may be considered.
Ideal Experience 5+ years in Analytics Engineering Hands-on experience with Snowplow Unified migrations Experience with user stitching/identity resolution and the Conversions module Strong SQL and dbt skills Experience modelling large-scale event data in Snowflake Snowplow Attribution experience is a strong advantage Timing Start as soon as possible.
Proposed delivery sequence: Unified package clean-up and migration User stitching implementation Attribution migration All changes should be validated alongside existing reporting before legacy models are retired.
