Frequently Asked Questions

Your Auric instance is available at https://YOUR-APP-ID.auriccloud.com where YOUR-APP-ID is your unique tenant identifier. You can find this in your welcome email or contact support if you're unsure.

Contacts are the people using your application, identified by their email address. Events are the actions those contacts take, like "signup", "purchase", or "download". One contact can have many events over time, forming their customer journey.

1. Go to Settings → Ingest and add your domain to "Allowed Origins"
2. Copy the JavaScript tracking code provided
3. Add it to your website before the closing </body> tag
4. Configure your default event type in the script
5. Test with ?test=true in your URL to see console debug output

The tracker automatically captures form submissions and email addresses.

Common issues:

• Origin not allowed: Add your domain to Settings → Ingest → Allowed Origins
• No email detected: Ensure email inputs are properly named or typed
• Event type not configured: Set defaultEventType in your config
• JavaScript errors: Check browser console for errors
• Form navigation too fast: The tracker includes timing delays for this

Add ?test=true to your URL to see debug information in the console.

New-to-File: The very first event for a contact (always marked on their First Touch event).
Reactivation: When a contact returns after your reactivation window (default 90 days). This helps identify returning customers vs. continuously active ones. You can adjust the reactivation window in Settings.

Use the CSV import feature on the Import page:

1. Download the CSV templates for contacts or events
2. Fill in your data using the required columns
3. Upload the CSV file
4. Review the import results for any errors

The system will automatically create contacts and assign First Touch events during import.

Yes, you can delete contacts from the Contacts page. When you delete a contact, all their associated events are also permanently deleted. This action requires confirmation and cannot be undone. For data privacy compliance, this provides a way to fully remove customer data when requested.

Custom fields let you store additional information beyond the standard fields:

• Contact fields: Store info about the person (company, role, phone)
• Event fields: Store action-specific data (purchase amount, plan type)

Create them in Settings, then they'll appear in forms, imports, and API calls automatically.

1. Go to Settings → API Keys
2. Enter a descriptive name for your integration
3. Click "Create API Key"
4. Copy the key immediately - it's only shown once
5. Use it in the Authorization header: Bearer YOUR_API_KEY

You can create multiple API keys for different integrations and revoke them individually.

/i (Public endpoint):

• For client-side JavaScript tracking
• Uses CORS/origin authentication
• Optimized for web browsers
• No API key required

/api/events (API endpoint):

• For server-to-server integration
• Requires API key authentication
• Supports bulk operations
• Higher rate limits

• Public /i: 1000/hour per origin, 100/minute burst
• /api/events: 5000/hour per API key, 500/minute burst
• /api/contacts: 1000/hour per API key, 100/minute burst

Rate limit headers in responses show your remaining quota. Contact support if you need higher limits.

• 400 Bad Request: Check your JSON format and required fields (email, event_type)
• 401 Unauthorized: Verify your API key is correct and included in Authorization header
• 403 Forbidden: For /i endpoint, ensure your domain is in Allowed Origins

Use the API documentation examples and test with cURL first to isolate the issue.

Dashboard metrics update in real-time as new events are processed. If they're not updating:

1. Verify events are being successfully created (check Events page)
2. Refresh the dashboard page
3. Check that events have valid timestamps
4. Ensure events are associated with the correct tenant

If the issue persists, contact support with specific details.

1. Add ?test=true to your URL to enable debug mode
2. Open browser developer tools (F12) and check the Console tab
3. Look for Auric debug messages showing email detection and event sending
4. Check the Network tab for requests to /i endpoint
5. Verify the response status and any error messages
6. Test manual tracking: AURIC.track('test_event', {test: true})