Managing Packets
Packets are groups of documents that users accept together. They allow you to bundle related legal agreements and present them as a cohesive unit during user signup or other key moments.
Accessing Packets
To manage your packets, navigate to https://app.toughclicks.com/packet in the Management Portal.
From this page, you can:
- View all your packets
- Create new packets
- Edit packet composition
- Find the Packet ID needed for integration
What is a Packet?
A packet is a collection of documents that are presented to users together. Think of it as a bundle of legal agreements.
Common Examples:
- User Registration Packet: Terms of Service + Privacy Policy
- Enterprise Signup Packet: Terms of Service + Privacy Policy + SLA + DPA
- Mobile App Packet: Terms of Service + Privacy Policy + Mobile-specific Terms
- Beta Program Packet: Beta Terms + NDA + Standard Terms
Creating a Packet
- Click Create Packet on the packets page
- Enter a descriptive name (e.g., "User Registration Packet")
- Optionally add a description for internal reference
- Click Save
Your packet is now created and ready to have documents added.
Adding Documents to a Packet
- Click on the packet row to open the packet details
- Click Add Document
- Select from your available documents
- Set the display order (documents will appear in this order to users)
- Click Save
You can add multiple documents to create a comprehensive acceptance flow.
Document Order
The order of documents in a packet matters:
- Documents are displayed to users in the specified order
- Users must typically accept all documents in the packet
- Consider logical grouping (e.g., Terms of Service first, then Privacy Policy)
Removing Documents from a Packet
- Open the packet details
- Click the remove icon next to the document you want to remove
- Confirm the removal
If you remove a document from a packet that's actively being used in your application, users will no longer see that document during the acceptance flow. Make sure this is intentional.
Finding Your Packet ID
The Packet ID is crucial for your integration - it's what you'll use in your code to reference which documents users should accept.
To find your Packet ID:
- Navigate to the packets page
- Look in the packets table - each row shows the Packet ID
- You can also find it in the packet details page
- Copy the ID to use in your integration code
Example Packet ID: pkt_abc123def456
You'll use the Packet ID when initializing the ToughClicks library:
const tc = new ToughClicks({
clientId: 'your-client-id',
packetId: 'pkt_abc123def456' // Your Packet ID here
});
Packet Use Cases
Multiple Packets for Different Flows
You might want different packets for different user journeys:
| Packet Name | Documents | Use Case |
|---|---|---|
| Basic Signup | ToS + Privacy | Free tier users |
| Premium Signup | ToS + Privacy + SLA | Paid users |
| Enterprise Signup | ToS + Privacy + SLA + DPA + BAA | Enterprise customers |
Regional Variations
Create separate packets for different regions:
- US Packet: US Terms + US Privacy Policy + California-specific addendum
- EU Packet: EU Terms + GDPR Privacy Policy + Cookie Policy
- Global Packet: International Terms + Global Privacy Policy
Version-Specific Packets
For A/B testing or gradual rollouts:
- Beta Packet: Next version of terms for beta users
- Standard Packet: Current production terms
- Legacy Packet: Previous terms for grandfathered users
Managing Active Packets
Editing a Packet
- Click on the packet to open details
- You can modify:
- Packet name and description
- Included documents
- Document order
- Display method, and the submit button label when using Button Assent
- Changes take effect immediately
Display Method
The Configurations tab sets the packet's default display method: Individual, Group, Force Scroll, or Button Assent. An integration that sets a display method in code overrides this default.
Choosing Button Assent reveals a required Submit button label field. Enter the label of the button on the integrator's page, exactly as it appears there — the notice reads "By clicking <label> you agree to…", and the label is printed on the acceptance certificate. The packet cannot be saved in this mode without one.
Button Assent displays a notice with no checkbox: clicking the site's own submit button is the agreement. It reduces friction at checkout, but its enforceability depends on the notice sitting directly beside that button, and no part of ToughClicks can enforce that placement — only the integrator can. Prefer a checkbox method wherever the extra click is acceptable, and see Display Methods for placement guidance.
Modifications to active packets affect your live integration immediately. Test changes in a sandbox environment first if possible.
Deactivating a Packet
To stop using a packet without deleting it:
- Remove all documents from the packet, or
- Note in the description that it's deprecated
- Update your integration to use a different packet
Cloning a Packet
To create a similar packet:
- Create a new packet with a new name
- Add the same documents as the original
- Adjust as needed for the new use case
This is useful for creating regional or versioned variations.
Best Practices
Naming Conventions
- Use descriptive, meaningful names
- Include context (e.g., "Production User Signup" vs. "Beta User Signup")
- Consider including environment (e.g., "Sandbox - User Registration")
- Use consistent naming across your organization
Document Selection
- Only include documents relevant to the specific use case
- Keep packets focused and purposeful
- Don't overwhelm users with unnecessary documents
- Group related documents together
Organization Strategy
- Create separate packets for different user types
- Use different packets for different features or access levels
- Maintain both sandbox and production packets
- Document the purpose of each packet in the description
Maintenance
- Regularly review active packets
- Remove or update obsolete packets
- Keep packet documentation up to date
- Coordinate packet changes with deployment schedules
Integration Examples
Basic Integration
// Single packet for all users
const tc = new ToughClicks({
clientId: 'cli_abc123',
packetId: 'pkt_user_signup' // Standard user registration
});
Conditional Packets
// Different packets based on user type
const packetId = user.isPremium
? 'pkt_premium_signup'
: 'pkt_basic_signup';
const tc = new ToughClicks({
clientId: 'cli_abc123',
packetId: packetId
});
Regional Packets
// Different packets based on user location
const getPacketForRegion = (region) => {
const packets = {
'US': 'pkt_us_signup',
'EU': 'pkt_eu_gdpr_signup',
'DEFAULT': 'pkt_global_signup'
};
return packets[region] || packets.DEFAULT;
};
const tc = new ToughClicks({
clientId: 'cli_abc123',
packetId: getPacketForRegion(user.region)
});
Troubleshooting
Packet ID not working in integration
- Verify you're using the correct Packet ID from the Management Portal
- Check that the packet contains at least one published document version
- Ensure the packet hasn't been deleted
- Verify your client has access to this packet
Documents not appearing in order
- Check the document order settings in the packet details
- Ensure all documents have explicit order numbers
- Re-save the packet if order seems incorrect
Users seeing old document versions
- Verify the latest version of each document is published
- Check that documents in the packet reference the correct versions
- Clear any application-level caching
- Verify the packet configuration is correct