How do I copy/clone an event in Grip?

Learn how to efficiently duplicate events within the same or different Grip applications.

Copying successful events in Grip allows event organizers to save time and streamline the setup of new events. This feature is particularly beneficial for those managing multiple events across various Grip applications. In this article, you'll learn how to copy events within the same application or across different applications, and what settings and data are included in the process.

In this article, we will cover:

  • How to Copy an Event
    • Copying an Event within the Same Grip Application
    • Copying an Event from a Different Grip Application
  • What Does and Does Not Get Copied
    • Data Types, Settings, and Permissions
    • Navigation Items and Settings
    • Homepage Items and Settings
    • Campaign/Welcome Emails
    • Event Settings
    • Meeting Settings
    • Native Integrations
    • Custom Groups
    • Event Agenda Items
  • FAQ

 

     

    How to copy an event


    Grip offers two types of event copying: within the same application and across different applications.

    Copying an Event within the Same Grip Application

    To copy an event within the same Grip application:

    1. Select the Event: Navigate to the event you want to duplicate.
    2. Click the Copy icon: This initiates the event cloning process.
    3. Adjust settings as needed: This allows you to replicate the event setup quickly and efficiently, avoiding repetitive configuration tasks.

    Copying an Event from a Different Grip Application

    To copy an event from a different Grip application:

    To copy an event from a different Grip application:

    1. Enable Copying Permissions: In the source event, go to Event Details > Event Setup > Event Template Settings and enable copying by using the template code.

    2. Go to the Target Application: Select Create New Event > Copy an Event from Another App.

    3. Paste the Template Code: Enter the template code, validate it, and proceed.

    4. Map Data Types: Ensure the target application supports all data types from the source event. Mapping is required for this step.

      Caution: You cannot copy an event if your application does not support the same or a larger amount of data types as the source event. Ensure proper mapping before proceeding. 

    5. Toggle Setup Features: Select which event features to copy by toggling them on or off based on compatibility and your needs.

    6. Finalize Event Details: Enter the event name, location, start and end dates, and click Create New Event. Your pre-configured event will be ready in just a few minutes!



    What gets copied and what does not when I copy an event?

    Data Types, Settings, and Permissions

    • Copied: All event data types, settings, permissions, relationships, and custom profile fields are copied at both the app and event levels.
    • Not Copied: Event name, location, start date, and end date must be manually entered.

    Navigation Items and Settings

    • Copied: All navigation items and settings, including custom groups and platform settings.

    Homepage Items and Settings

    • Copied: All blocks, text, background colors, thumbnails, visibility permissions, and platform settings.

    Campaign/Welcome Emails

    • Copied: All email settings, including automated email toggles (whether in-app or cross-app), templates, and email names, are copied when using event templating. However, email analytics and sending data are not included in the copy.

    Email analytics are not included. This is because this only refers to emails sent in the specific event, so this information will be redundant in a new event.

    Event Settings

    • Copied: Default event access, industry, format, date and time formats, platforms, email sending domain, notification queue, and registration queue settings.

    Meeting Settings

    • Copied: Group meeting settings, instant meeting settings, and default meeting location capacity.

    Native Integrations

    • Copied: All settings and mappings, excluding integration schedules.

    Custom Groups

    • Copied: Group names (with translations), recommendations, profile visibility, search capabilities, and unstructured metadata.

    Event Agenda Items

    • Copied: As per the feature list.

    FAQs

                  

    Q: Can I copy a copied event?

    • A: Yes, you can copy a copied event.

    Q: Can I copy events from one Grip Application to another?

    • A: Yes, you will need the template code of the source event. The steps for cross-application copying are covered in this article.

    Q: Does the Custom Group ID stay the same or is it different in the copied event?

    • A: No, the Custom Group IDs are different in both events.

    Q: Does this copy MustMeet settings?

    • A: Yes, it’s shown in the features list (if the event you’re copying is a MustMeet event).

    Q: Does this copy meeting settings?

    • A: At present, this does not include meeting settings as it requires timings to be specified. 

    Q: Is it possible to transfer data profiles from one event to another?

    • A: No, profiles cannot be copied, as each would require a new registration ID. However, you can utilize Native Integrations to import profiles from  different events.