Setup Invisible Landing Page (Auto-Redirect) + Facebook Pixel Custom Event for “Add LINE”

Job Post — Invisible Redirect Landing Page + Facebook Pixel Event for “Add LINE”

Project Title:
Setup Invisible Landing Page (Auto-Redirect) + Facebook Pixel Custom Event for “Add LINE”

Goal (must achieve):
When a user clicks my ad, they arrive on an invisible redirect page that immediately fires a Facebook Pixel custom event (e.g., AddLine_Click) and auto-redirects to my LINE invite. Users should not feel there is an extra step. The custom event must appear in Facebook Ads Manager → Events Manager for optimization.

----

Requirements (強化版)
• Must test on all major devices:
• iPhone (Safari), Android (Chrome), Desktop (Chrome/Edge).
• Cross-device testing is mandatory. No exceptions.
• Must provide visual proof:
• Screenshots from Facebook Events Manager clearly showing the custom event AddLine_Click, including:
• Event name
• Recent activity log
• Parameters (source, device)
• Proof must be included in delivery.
• Work will NOT be accepted without verification:
• Delivery is incomplete unless cross-device test results + Events Manager screenshots are provided.
• Payment release will only happen after proof is confirmed.




⸻

1) Scope of Work (do exactly these)

A. Build an invisible auto-redirect page (single HTML file)
• No visible UI for users in normal flow (no big buttons, no texts).
• On page load:
1. Fire Pixel custom event AddLine_Click (see details below).
2. Immediately redirect to LINE using this sequence:
• Mobile (iOS/Android):
• Try deep link first: line://ti/p/@MY_ID
• After ~600–800ms, fallback to web link: https://line.me/R/ti/p/@MY_ID
• Desktop:
• Open web link https://line.me/R/ti/p/@MY_ID in a new tab/window.
• Add a testing mode (e.g., ?debug=1) that temporarily disables auto-redirect and shows a simple page with:
• “Add LINE” button (links to the web link)
• The QR code generated from the same web link
This is only for QA. In normal use (no debug), users must not see any page.

B. Facebook Pixel integration & event firing
• Add Pixel base code (help me create a Pixel ID if I don’t have one).
• On page load (before redirect), fire:

fbq('trackCustom', 'AddLine_Click', {
source: 'auto_redirect',
device: (isMobile ? 'mobile' : 'desktop')
});

• Ensure the event is sent before navigating away. Use a small delay (~150–300ms) or navigator.sendBeacon/keepalive techniques so the hit is reliably delivered without hurting UX.

C. Fallbacks & resilience
• Provide meta refresh and noscript fallbacks to the LINE web link, in case JavaScript is disabled.
• If deep link fails on mobile, web link fallback must still open.

D. Testing & verification (must provide evidence)
• Test on iPhone (Safari), Android (Chrome), and Desktop (Chrome/Edge).
• In Events Manager, confirm AddLine_Click is received (show screenshots with event name, recent activity, and parameters source / device).
• Confirm the redirect timing is smooth (user shouldn’t perceive an extra step; total added delay ≈ 150–300ms before navigation begins).

⸻

2) Technical Details (please follow)
• Device detection:
Use UA sniffing or feature checks to distinguish mobile vs desktop for the redirect strategy.
• Redirect logic (pseudo):

const isMobile = /Android|iPhone|iPad|iPod/i.test(navigator.userAgent);
const LINE_WEB = 'https://line.me/R/ti/p/@MY_ID';
const LINE_DEEP = 'line://ti/p/@MY_ID';

function firePixel() {
fbq('trackCustom', 'AddLine_Click', {
source: 'auto_redirect',
device: isMobile ? 'mobile' : 'desktop'
});
}

function go() {
if (isMobile) {
// Try deep link first
window.location.href = LINE_DEEP;
// Fallback to web link after ~700ms
setTimeout(() => { window.location.href = LINE_WEB; }, 700);
} else {
// Desktop: open web link
window.location.href = LINE_WEB;
}
}

// On load
firePixel();
setTimeout(go, 200); // small delay to let Pixel send


• QR code:
Not shown in normal flow. In ?debug=1 mode, generate QR from LINE_WEB and display for QA only.
• Hosting:
Any static hosting is fine (single HTML/CSS/JS). Provide files (zip/repo) and a temporary live URL.

⸻

3) Deliverables
1. Live URL of the invisible redirect page (for connecting the ad).
2. Source files (HTML/CSS/JS) in a zip or repository.
3. Pixel integrated; AddLine_Click fires on page load before redirect.
4. Screenshots from Facebook Events Manager showing:
• Event name AddLine_Click
• Recent activity received
• Parameters source and device
5. A short README with:
• How to replace my LINE ID (@MY_ID)
• Where to paste my Pixel ID
• How to enable/disable ?debug=1 mode

⸻

4) What I will provide
• my LINE invite link (web URL),

• I don’t have a Pixel ID yet, please guide me to create one in Ads Manager (or I’ll grant limited access so you can help).

⸻

5) Budget & Timeline
• Budget: ~US$100 for Invisible Page + Pixel + Event setup
• Timeline: 1–3 days

⸻

6) Acceptance Criteria
• Normal users do not see a landing page; they feel one-tap to LINE.
• On page load, AddLine_Click fires and is visible in Events Manager.
• Redirect is immediate and smooth (≈200ms pre-navigation; deep-link fallback ≈700ms).
• Desktop opens the LINE web link; mobile tries deep link then falls back to web link.
• ?debug=1 shows a simple test page with “Add LINE” button + QR (for QA only).
• Provide Events Manager screenshots as proof.

⸻

Notes for freelancers (re: LINE)
• LINE is a chat app popular in Taiwan/Japan/SEA (similar to WhatsApp).
• Web invite link format: https://line.me/R/ti/p/@MY_ID
• Mobile deep link: line://ti/p/@MY_ID
• We are not tracking inside the LINE app; we only track the click/arrival that opens LINE.