Set up integrations with JUNO

Integration is a way to transfer information from your data management system to your JUNO platform. The development of any integration is a team effort between the Client team and JUNO team. This guide outlines that process so that you know what to expect.

When to use integration

Integration is an alternative to importing users, using JUNO’s free registration, and/or importing content. It’s an extra cost that’s agreed upon in the contract process.

With API registration integration and Single Sign On (SSO) integration, our goal is to get users registered on the site. With content integration, our goal is to get content onto the site.

API registration or SSO integration process

The process is the same for both types of integrations.

1. Gather information after kickoff

We need to understand your data, data management system, and goals. This helps us get on the same page so that we can smoothly move data from your system into the JUNO system.

After the kickoff meeting, the JUNO Success Manager sends the Client team a Google form and allowlist to complete as homework.

2. Integrations meeting

During the meeting, the JUNO Success Manager, JUNO Integrations Team, and Client team walk through the mapping document and requirements.

Agenda: 

• Walk through the tabs of the mapping document.

• Go over any specific access codes; Staff, Exhibitor, etc.

• Discuss any specific dimensions JUNO should be pulling over from registration; City, Country, etc.

• Discuss any business rules.

• Discuss attendee communication (see above).

• If JUNO is sending email/password or magic links, go over email template and if passwords will be randomly generated or universal.

• The Client team will provide images and copy for the email template.

The JUNO Success Manager sends the Client team the mapping document and training video to complete as homework.

3. Test the endpoint

1. The JUNO team pulls the payload to ensure we can access the endpoint. They’ll check the attendee count, then share it with the Client team.

2. If the Client team confirms the count is correct, it’s time for JUNO to begin coding.

4. Coding begins

Then we test the data to make sure everything works and you’re happy with how the integration is set up.

1. The JUNO Success Manager gives the mapping document to the JUNO Development team. They also add the Client team’s tags to the platform.

2. As the JUNO Development team codes, they might pass along questions to the Client team, or join a meeting.

5. Review

1. On a weekly call, the JUNO Success Manager reviews a small sample of each user type with the Client team. Together, they look at the user information in the content management system, on the profile page and profile page editor, and in the directory.

2. If needed, the JUNO Development team makes edits.

6. Final build

1. The JUNO Success Manager makes sure JUNO team members are registered in the Client team’s system.

2. The JUNO Development team pushes the build from the testing environment (.dev) to the live production site.

3. The Client team tests users on the production site to ensure the integration is flowing correctly. 

Content integration process

1. Gather information after kickoff

We need to understand your data, data management system, and goals. This helps us get on the same page so that we can smoothly move data from your system into the JUNO system.

After the kickoff meeting, the JUNO Success Manager sends the Client team a Google form and allowlist to complete as homework, along with a mapping document to review.

2. Collecting content meeting

During the content meeting, the JUNO Success Manager and Client team discuss the mapping document.

Agenda:

• Review theContent Integration Form.

• Review key milestones and timelines.

• Review mapping document needs. Discuss each type of content and discuss how to fill the document out.

3. Integrations meeting

Using the completed homework documents, the JUNO Integrations team pulls an initial payload of information before the meeting.

Then during the meeting, the JUNO Success Manager, JUNO Integrations Team, and Client team walk through the mapping document and requirements.

Agenda:

• Review each tab of the Content Mapping Document.

• Address questions from the Integrations Team.

• Discuss necessary edits.

• Discuss a due date for edits and action items.

4. Pull a sample payload

We test the data to make sure everything works and you’re happy with how the integration is set up.

1. The JUNO Success Manager gives the mapping document to the JUNO Development team. They also add the Client team’s tags to the platform.

2. The JUNO team pulls a sample payload and imports the sample onto the site. There are 2-3 pieces of content per content type.

5. Review sample

On a weekly call, the JUNO Success Manager reviews the content samples with the Client team. They look at the content on the site to make sure it looks correct. They note change requests for the JUNO Integrations team.

6. Pull full payload

The JUNO team pulls the full payload and the JUNO Development team begins coding. If they have questions, they pass them along to the Client team or join a meeting.

7. Review full mapping

1. On a weekly call, the JUNO Success Manager reviews the content with the Client team. They look at the content on the site to make sure it looks correct.

2. If needed, the JUNO Development team makes edits.

8. Final build

The JUNO Development team pushes the build from the testing environment (.dev) to the live production site. Integration is complete!