Traffic is captured from Fastly logs, so the website does not need browser-side tracking code for this integration.
Add Siteline to Fastlythrough CDN logs
This demo explains Siteline's Fastly option in plain language. Fastly writes traffic logs to Amazon S3, and a small AWS Lambda processor forwards pageview events to Siteline.
For teams using Fastly CDN logging, AWS, and a Siteline website key.Connected Siteline website
This protected demo check uses Supabase auth, then reads the website and product connected to this app's configured Siteline website key.
Authentication required
Unlock the configured Fastly website
Use a Siteline account that has access to the website represented by this app's environment key. The website key stays server-side and is never printed in full.
Integration option
A log processor for existing Fastly traffic
The Fastly integration is for teams that want Siteline to receive pageview events from server-side CDN logs. It does not sit inside your website. It reads Fastly log files after Fastly delivers traffic.
Fastly keeps serving your site. The integration adds an S3 logging endpoint and an AWS processor beside it.
The setup scripts create or update S3, Lambda, EventBridge, IAM, and the Fastly logging endpoint in a repeatable way.
How it works in plain English
Think of this as a delivery receipt pipeline. Fastly serves the website as usual, writes receipts to S3, and AWS sends the useful pageview details to Siteline.
Fastly serves website traffic
Your existing Fastly service continues to deliver pages to visitors and AI agents.
Fastly writes logs to S3
A Fastly S3 logging endpoint sends newline-delimited JSON log files to an Amazon S3 bucket.
AWS notices new log files
S3 object-created events flow through EventBridge and trigger the Lambda processor.
Siteline receives pageview events
The Lambda reads valid log rows, maps fields such as URL, status, user agent, referrer, IP, and duration, then forwards events to Siteline.
Short setup documentation
This is the short version for a non-technical review. A technical teammate can use the repository commands when it is time to deploy.
Prerequisites
- Node.js 18+ and npm.
- AWS CLI access with permission to manage S3, Lambda, IAM, and EventBridge.
- A Fastly API token with service write access.
- Fastly S3 logging credentials.
- Your Siteline website key.
Fill the environment file
- Copy the example environment file.
- Set the Siteline website key.
- Set the S3 bucket, AWS region, Fastly service, API token, and Fastly S3 credentials.
cp .env.example .envPackage and create the pipeline
- Install dependencies.
- Package the Lambda processor.
- Run the setup script that configures S3, Lambda, EventBridge, and Fastly logging.
- Run CI checks when validating changes.
npm install
npm run package
npm run setup:all
npm run ciFastly integration FAQ
Short answers for teams deciding whether this is the right Siteline integration option.
Does this run on the website itself?
No. This option processes Fastly CDN logs after traffic is served. It does not require adding browser JavaScript to your site.
Why does it need AWS?
Fastly sends logs to S3. AWS EventBridge and Lambda then pick up new log files and forward pageview events to Siteline.
Is it real time?
It is near real time, but Fastly log delivery can be delayed by buffering periods. It is better described as a log processing pipeline than an instant request hook.
What does the processor send?
It maps valid log rows into pageview events with fields like URL, method, status, duration, user agent, referrer, and IP.
Use the Fastly processor when CDN logs are your source of truth
It is the right option when your team wants Siteline events from Fastly delivery logs and is comfortable managing the AWS pipeline beside Fastly.