المهارات server-side-conversion-tracking
📦
server-side-conversion-tracking
مراجعة المحتوى r1 مخاطر متوسطة ⚡ يحتوي على سكربتات⚙️ الأوامر الخارجية🌐 الوصول إلى الشبكة
Build Reliable Server-Side Conversion Tracking
Browser restrictions and cross-domain funnels cause advertising platforms to miss purchases. This skill designs a durable capture, reporting, deduplication, and verification workflow.
يدعم: Claude Codex Code(CC)
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
طلب الوكيل
Review the Skillstore skill "server-side-conversion-tracking" from https://skillstore.io/skills/autonnel-server-side-conversion-tracking.md and its manifest at https://skillstore.io/api/skills/autonnel-server-side-conversion-tracking/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "server-side-conversion-tracking". Facebook reports 62 purchases, while the order database records 100. Only 48 paid orders contain fbclid.
النتيجة المتوقعة:
- Primary finding: click identifier loss likely occurs before the order record.
- Inspect landing capture, redirects, session persistence, and cross-domain checkout transfer.
- Track daily click identifier coverage and compare it with the paid traffic share.
جارٍ استخدام "server-side-conversion-tracking". A browser pixel and server event both report each purchase, but totals nearly doubled after launch.
النتيجة المتوقعة:
- Primary finding: browser and server events probably use different event identifiers.
- Generate one stable purchase event identifier and send it through both delivery paths.
- Confirm deduplication in the platform debugger before scaling traffic.
جارٍ استخدام "server-side-conversion-tracking". Plan server-side purchase reporting for Facebook, TikTok, Google Ads, and Microsoft Advertising.
النتيجة المتوقعة:
- Capture each platform click identifier and campaign parameters on the first landing request.
- Persist identifiers server-side, carry them across domains, and attach them to the order.
- Queue platform deliveries with normalized customer identifiers, retries, deduplication, and reconciliation checks.
التدقيق الأمني
مخاطر متوسطةv1 • ٥/٨/٢٠٢٦ فتح التقرير المرتبط بالإصدار
Most static findings are Markdown syntax and conversion-tracking terminology, not executable code or system reconnaissance. The skill does recommend running Docker Compose from a remote repository and describes collecting and transmitting privacy-sensitive customer data.
1
الملفات التي تم فحصها
109
الأسطر التي تم تحليلها
1
عناصر المراجعة
0
تم تجاهل الإيجابيات الكاذبة
مخاوف أمنية مؤكدة (2)
متوسط
Privacy-Sensitive Customer Data Workflow
The workflow collects client IP addresses, user agents, click identifiers, and hashed customer identifiers for transmission to advertising platforms. Consent is acknowledged, but retention and access controls are not defined.
The listed fields and intended third-party transmission are explicit. The skill also states that hashed personal information remains personal information.
متوسط
Unpinned Remote Container Execution
The setup recommends checking out a release tag and running Docker Compose from a remote repository. Mutable tags and unpinned images can introduce supply-chain changes.
The instructions explicitly combine a remote repository, a release tag, and Docker Compose execution. No immutable commit or container image digest is required.
عناصر مراجعة القدرات (1)
هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.
متوسط
Ruby/shell backtick execution
```bash
Lines 101-104 instruct the user to run docker compose up from a downloaded repository. This starts externally defined containers and can execute images or mounts declared by that repository.
عوامل الخطر
⚡ يحتوي على سكربتات (1)
⚙️ الأوامر الخارجية (12)
🌐 الوصول إلى الشبكة (3)
دقّقه: codex
شارك واستشهد بهذا التقرير
شارك تقرير التقييم المرتبط بالإصدار والشارة المحايدة وبطاقة التضمين والاستشهادات. تعرض Skillstore الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/autonnel-server-side-conversion-tracking/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](https://skillstore.io/skills/autonnel-server-side-conversion-tracking?utm_source=security_passport_badge)شارة HTML
<a href="https://skillstore.io/skills/autonnel-server-side-conversion-tracking?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/autonnel-server-side-conversion-tracking/security.svg" alt="Skillstore security assessment" loading="lazy"></a>بطاقة قابلة للتضمين
<iframe src="https://skillstore.io/embed/skills/autonnel-server-side-conversion-tracking.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>الاستشهادات الأكاديمية (APA · BibTeX · CFF)
اقتباس APA
autonnel. (2026). server-side-conversion-tracking security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/autonnel-server-side-conversion-tracking/audits/1اقتباس BibTeX
@techreport{autonnel-autonnel-server-side-conversion-tracking-2026,
author = {autonnel},
title = {server-side-conversion-tracking security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/autonnel-server-side-conversion-tracking/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "server-side-conversion-tracking security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "autonnel"
date-released: "2026-08-05"
url: "https://skillstore.io/skills/autonnel-server-side-conversion-tracking/audits/1"
identifiers:
- type: other
value: "skillstore:autonnel-server-side-conversion-tracking:audit:1"
description: "Skillstore immutable audit report identifier"
تقييم Skillstore
سبب هذا التقييم موثوقية الأدلة: متوسط 55
الهندسة المعمارية
85
قابلية الصيانة
87
المحتوى
65
المجتمع
83
الامتثال للمواصفات
ما الذي يمكنك بناؤه
Repair Under-Reported Purchases
Trace where campaign identifiers or purchase events disappear, then define fixes and measurable verification checks.
Design a New Tracking Pipeline
Plan capture, persistence, order attachment, queued delivery, and deduplication before paid traffic begins.
Reconcile Platform Reporting
Compare advertising conversions with order records while accounting for attribution windows and different reporting dates.
جرّب هذه الموجّهات
Review My Tracking Setup
Review my current funnel for server-side conversion tracking. Platforms: [platforms]. Funnel steps: [steps]. Domains: [domains]. Identify missing stages and priorities.
Plan Click Identifier Capture
Design click identifier and UTM capture for [funnel]. Explain server-side persistence, cross-domain transfer, order storage, and failure checks.
Specify Conversion Delivery
Create a platform-by-platform delivery specification for [platforms]. Include event fields, identifier normalization, credential needs, queue retries, and browser-server deduplication.
Diagnose Reporting Gaps
Diagnose this reporting gap using [order totals], [platform totals], [click identifier coverage], and [debugger results]. Separate tracking loss from attribution differences.
أفضل الممارسات
- Capture campaign identifiers before redirects and persist them in a first-party server session.
- Use one stable purchase event identifier for browser and server events.
- Verify delivery, match quality, click identifier coverage, and order reconciliation after every tracking change.
تجنب
- Do not add only a server event while ignoring identifier capture and order attachment.
- Do not send conversion requests inline with payment or checkout processing.
- Do not treat hashed customer data as anonymous or bypass consent requirements.
الأسئلة المتكررة
Does server-side tracking recover every missing conversion?
No. It improves delivery and matching, but consent restrictions, missing identifiers, and attribution rules still affect reported totals.
Why must click identifiers be stored on the order?
Order storage survives session loss, supports retries and backfills, and enables reliable joins between purchases and advertising clicks.
How are duplicate browser and server events prevented?
Both paths must send the same stable event identifier for each purchase. Platform debuggers should confirm successful deduplication.
Should platform totals equal database orders?
No. Attribution windows, view-through credit, click dates, and platform-specific rules create expected differences.
Is hashed customer information still personal data?
Yes. Apply consent, access, retention, deletion, and regional privacy requirements before collecting or transmitting it.
Can this skill configure every advertising account automatically?
No. It provides implementation and verification guidance. Credentials, account permissions, platform settings, and current API requirements need direct validation.