Q: What type of widgets are available in DirectoryPopup?

Widget Types Pop-up https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/EcSOmYqpuC/popup.jpg (popup.jpg) Features There is almost no way for a visitor to miss the information, that is shown in a pop-up. The size of this widget allows you to use multiple and big enough (compared to other widgets) elements, like background images, text boxes, multiple fields for subscriber information, etc. Scroll Box https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/9kqRuSyHPd/scroll-box.jpg (scroll-box.jpg) Features Attracts visitor's attention without overlapping the content, disturbing from reading. In general, big enough for complex vertical-oriented content blocks. Floating Bar https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/JrsC5s3dVp/floating-bar.jpg (floating-bar.jpg) Features It covers a small part of visitor's screen, thus not disturbing from reading the content. A good choice for short messages like cookie notification and compact forms without much of a content. Welcome Screen https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/pg2ZKexfOc/welcome-screen.jpg (welcome-screen.jpg) Features There is no way for a visitor to miss the information. The size of this widget allows using a lot of different content inside it. Inline https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/EJNCpV7H0U/inline.jpg (inline.jpg) Features Widgets of this type never overlap the content and thus not disturbing the visitor from reading. Could be placed anywhere and used to create forms related to the particular part of the page content.

Question 1

What type of widgets are available in DirectoryPopup?

Accepted Answer

Widget Types

Pop-up

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/EcSOmYqpuC/popup.jpg (popup.jpg)

Features

There is almost no way for a visitor to miss the information, that is shown in a pop-up.
The size of this widget allows you to use multiple and big enough (compared to other widgets) elements, like background images, text boxes, multiple fields for subscriber information, etc.

Scroll Box

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/9kqRuSyHPd/scroll-box.jpg (scroll-box.jpg)

Features

Attracts visitor's attention without overlapping the content, disturbing from reading.
In general, big enough for complex vertical-oriented content blocks.

Floating Bar

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/JrsC5s3dVp/floating-bar.jpg (floating-bar.jpg)

Features

It covers a small part of visitor's screen, thus not disturbing from reading the content.
A good choice for short messages like cookie notification and compact forms without much of a content.

Welcome Screen

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/pg2ZKexfOc/welcome-screen.jpg (welcome-screen.jpg)

Features

There is no way for a visitor to miss the information.
The size of this widget allows using a lot of different content inside it.

Inline

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/EJNCpV7H0U/inline.jpg (inline.jpg)

Features

Widgets of this type never overlap the content and thus not disturbing the visitor from reading.
Could be placed anywhere and used to create forms related to the particular part of the page content.

Question 2

What types of content does DirectorySlider work with?

Accepted Answer

DirectorySlider works with existing listings or posts in your directory or now add a custom slide with your own images!

Question 3

Why do my Yelp reviews not have authors?

Accepted Answer

The DirectoryImport tool uses Outscraper to import its data. Their data feed does not have the author for Yelp reviews included like it does for Google reviews. While we have a Yelp API connection, this API key is used to acquire the Yelp business ID only to use with Outscraper to pinpoint and import the reviews in bulk. So while the author is available from the Yelp API directly, the import tool uses an extreme amount of requests in short bursts to allow bulk loading of data. Having the Yelp API involved with this pull would trigger an issue with the Yelp API so we can’t use the Yelp APIs on the import tool to grab the author during that bulk upload process. If the author is still desired/required for the Yelp Reviews, we have made a tweak so that the reviews are loaded from Yelp instead of Outscraper on the front end DirectoryPhotos portion. So if you also have DirectoryPhotos plugin portion and a new member loads the reviews from the front end on their Photos tab, the Yelp reviews will now come with an author. We are basically using a slow pull allowed by the manual front end process to avoid Yelp issues, and to overcome an Outscraper limitation for Yelp that we cannot do in bulk on the Import backend tool. You can also fix existing reviews, but the member itself must be opened and the "Reload data" button must be clicked on each profile.

Question 4

Why is DirectoryImport only adding 3 Yelp reviews?

Accepted Answer

Currently the Yelp API only allows 3 reviews from its API endpoint to use in our tool. As a reminder the tool is used to provide seed content from Yelp and Google and is not intended to be a duplication or replacement or complete copy of other site content.

[figure]Yelp allows 3 reviews in their API endpoint[/figure]

Question 5

Working with URL & UTM parameters in DirectoryWebinar

Accepted Answer

What are URL parameters?

URL parameters (sometimes referred to as query strings) are text elements added to the end of a link (URL). These text elements generally consist of a "key" and a "value". Below you'll see a simple example of a link with URL parameters added on:

https://example.com/mypage ?traffic_source=google&another_key=another_value

The bold text is where the URL parameters start. In the above example, there are two key value pairs. One with the key "traffic_source" and the value "google". And the other with the key "another_key" and the value "another_value".

Essentially, you can use URL parameters to add extra data onto a link. Because of this, URL parameters are often used for analytics and tracking.

A common use case for why you would want to use URL parameters with DirectoryWebinar would be to track the traffic source of your event registrants. Say you're running ads on Facebook and Google for your event and you want to see which registrants are coming from Facebook and which are coming from Google.

When setting up your ads, you could add "traffic_source=google" to your Google ads link and traffic_source=facebook" to your Facebook ads.

Then whenever someone registers for your event, our system will store the URL parameters for that registrant. You could then view the URL parameters for each individual registrant, either in our built-in analytics or by exporting them to your own CRM/email platform, and see whether the registrant came from Google or Facebook.

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/x46J4DZT9l/directorywebinar-analytics.png (directorywebinar-analytics)

This is just one example but you can use URL parameters to add all sorts of analytics & tracking data to your links.

What are UTM parameters?

UTM parameters refer to 5 specific URL parameters that are commonly used in many analytics platforms. You can see them all below:

utm_source - Example: utm_source=google

utm_medium - Example: utm_medium=cpc

utm_campaign - Example: utm_campaign=spring_sale

utm_term - Example: utm_term=running+shoes

utm_content - Example: utm_content=textlink

How to pass in URL & UTM parameters to DirectoryWebinar?

When someone registers for your event (either on a registration page hosted on our platform or via an embedded form on your own website/custom landing page), DirectoryWebinar will store any URL parameters at the webpage the registrant is currently on.

So pretty much any URL/UTM parameters you add to your registration link will be stored along with the usual registration data (email, first name, last name, etc...).

How to view and retrieve URL & UTM parameters for my registrants?

The easiest way to view the URL parameters of your registrants is to open your event's analytics page and look at the "URL parameters" column. This data is also exported to the .csv file that is downloaded when you click the "Export Registrants" button.

If you'd like to send the URL parameters to a 3rd party application or CRM, currently we support 2 methods of doing this: Zapier and Webhooks. If you're using DirectoryCRM, you can use our "inbound webhooks" feature to receive DirectoryWebinar's webhook data. See the webhook section below for an example of that.

Zapier

You can use our Zapier app (Events Connecter) to pass along a registrant's URL parameters. Our Zapier integration makes it easy to grab each individual value from the URL parameters passed in.

Webhooks

You can also set up a webhook to send registrant data, including URL parameters, to a destination of your choosing. Similar to our Zapier integration, you can individually grab each key value pair from the URL parameters via the webhook request payload.

It's also worth noting that if you are a DirectoryCRM user, you can use our "inbound webhook" feature to receive the DirectoryWebinar webhook data fairly easily. In the following example, we show an example workflow that runs when an event registration occurs.

First, we create a DirectoryCRM Workflow and set it to trigger on an "inbound webhook".

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/2AFocgjnEv/DirectoryCRM-webhook.png (DirectoryCRM-webhook)

Then we grab the webhook URL provided by DirectoryCRM

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/wvog4xpwnj/DirectoryCRM-webhook-URL.png (DirectoryCRM-webhook-URL)

and paste that into our event settings in DirectoryWebinar (under the webhook section).

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/nPOti9TitU/directorywebinar-webhook.png (directorywebinar-webhook)

In order to update the correct contact with the URL parameters, we look up the contact we want with the email passed from the webhook.

https://malcolm-en-gb.s3.eu-west-1.amazonaws.com/instances/RftB9KeMum/resources/Qyp8mDoDPv/DirectoryCRM-webhook-name-lookup.png (DirectoryCRM-webhook-name-lookup)

Finally, we can do anything we want with the URL parameters passed from the webhook. In this example, we simply add the "utm_source" value to the contact's notes.