You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sources/academy/platform/get_most_of_actors/interact_with_users/emails_to_actor_users.md
+59-59Lines changed: 59 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,86 +38,88 @@ Our general policy is to avoid spamming users with unnecessary emails. We contac
38
38
39
39
New filter, faster scraping, changes in input schema, in output schema, a new Integration, etc.
40
40
41
-
✉️ 🏙️ Introducing Deep city search for Tripadvisor scrapers
42
-
43
-
Hi,
44
-
45
-
Tired of Tripadvisor's 3000 hotels-per-search limit? We've got your back. Say hello to our latest baked-in feature: Deep city search. Now, to get all results from a country-wide search you need to just set Max search results above 3000, and watch the magic happen.
46
-
47
-
A bit of context: while Tripadvisor never limited the search for restaurants or attractions, hotel search was a different case; it always capped at 3000. Our smart search is designed to overcome that limit by including every city within your chosen location. We scrape hotels from each one, ensuring no hidden gems slip through the cracks. This feature is available for [Tripadvisor Scraper](https://console.apify.com/actors/dbEyMBriog95Fv8CW/console) and [Tripadvisor Hotels Scraper](https://console.apify.com/actors/qx7G70MC4WBE273SM/console).
48
-
49
-
So get ready for an unbeatable hotel-hunting experience. Give it a spin, and let us know what you think!
50
-
51
-
→ introduce and explain the features, add a screenshot of a feature if it will show in the input schema, and ask for feedback.
41
+
>✉️ 🏙️ Introducing Deep city search for Tripadvisor scrapers
42
+
>
43
+
>Hi,
44
+
>
45
+
>Tired of Tripadvisor's 3000 hotels-per-search limit? We've got your back. Say hello to our latest baked-in feature: Deep city search. Now, to get all results from a country-wide search you need to just set Max search results above 3000, and watch the magic happen.
46
+
>
47
+
>A bit of context: while Tripadvisor never limited the search for restaurants or attractions, hotel search was a different case; it always capped at 3000. Our smart search is designed to overcome that limit by including every city within your chosen location. We scrape hotels from each one, ensuring no hidden gems slip through the cracks. This feature is available for [Tripadvisor Scraper](https://console.apify.com/actors/dbEyMBriog95Fv8CW/console) and [Tripadvisor Hotels Scraper](https://console.apify.com/actors/qx7G70MC4WBE273SM/console).
48
+
>
49
+
>So get ready for an unbeatable hotel-hunting experience. Give it a spin, and let us know what you think!
50
+
51
+
Introduce and explain the features, add a screenshot of a feature if it will show in the input schema, and ask for feedback.
52
52
53
53
### 2. Actor adapting to the changes of the website it scrapes
54
54
55
55
A common situation in web scraping that's out of your control.
56
56
57
-
✉️ 📣 Output changes for Facebook Ads Scraper
58
-
59
-
Hi,
60
-
61
-
We've got some news regarding your favorite Actor – [Facebook Ads Scraper](https://console.apify.com/actors/JJghSZmShuco4j9gJ/console). Recently, Facebook Ads have changed their data format. To keep our Actor running smoothly, we'll be adapting to these changes by slightly tweaking the Actor Output. Don't worry; it's a breeze! Some of the output data might just appear under new titles.
57
+
>✉️ 📣 Output changes for Facebook Ads Scraper
58
+
>
59
+
>Hi,
60
+
>
61
+
>We've got some news regarding your favorite Actor – [Facebook Ads Scraper](https://console.apify.com/actors/JJghSZmShuco4j9gJ/console). Recently, Facebook Ads have changed their data format. To keep our Actor running smoothly, we'll be adapting to these changes by slightly tweaking the Actor Output. Don't worry; it's a breeze! Some of the output data might just appear under new titles.
62
+
>
63
+
>This change will take place on October 10; please****make sure to remap your integrations accordingly.
64
+
>
65
+
>Need a hand or have questions? Our support team is just one friendly message away.
62
66
63
-
This change will take place on October 10; please****make sure to remap your integrations accordingly.
64
-
65
-
Need a hand or have questions? Our support team is just one friendly message away.
66
-
67
-
→ inform users about the reason for changes and how the changes impact them and the Actor + give them a date when the change takes effect.
67
+
Inform users about the reason for changes and how the changes impact them and the Actor + give them a date when the change takes effect.
68
68
69
69
### 3. Actor changing its payment model (from rental to pay-per-result, for example)
70
70
71
71
Email 1 (before the change, warning about deprecation).
72
72
73
-
✉️ 🛎 Changes to Booking Scraper
74
-
75
-
Hi,
76
-
77
-
We’ve got news regarding the Booking scraper you have been using. This change will happen in two steps:
78
-
79
-
1. On September 22, we will deprecate it, i.e., new users will not be able to find it in Store. You will still be able to use it though.
80
-
2. At the end of October, we will unpublish this Actor, and from that point on, you will not be able to use it anymore.
81
-
82
-
Please use this time to change your integrations to our new [Booking Scraper](https://apify.com/voyager/booking-scraper).
83
-
84
-
That’s it! If you have any questions or need more information, don’t hesitate to reach out.
85
-
86
-
→ warn the users about the deprecation and future unpublishing + add extra information about related Actors if applicable + give them steps and the date when the change takes effect.
73
+
>✉️ 🛎 Changes to Booking Scraper
74
+
>
75
+
>Hi,
76
+
>
77
+
>We’ve got news regarding the Booking scraper you have been using. This change will happen in two steps:
78
+
>
79
+
>1. On September 22, we will deprecate it, i.e., new users will not be able to find it in Store. You will still be able to use it though.
80
+
>2. At the end of October, we will unpublish this Actor, and from that point on, you will not be able to use it anymore.
81
+
>
82
+
>Please use this time to change your integrations to our new [Booking Scraper](https://apify.com/voyager/booking-scraper).
83
+
>
84
+
>That’s it! If you have any questions or need more information, don’t hesitate to reach out.
85
+
86
+
Warn the users about the deprecation and future unpublishing + add extra information about related Actors if applicable + give them steps and the date when the change takes effect.
87
87
88
88
Email 2 (after the change, warning about unpublishing)
89
89
90
-
✉️ **📢 Deprecated Booking Scraper will stop working as announced 📢**
91
-
92
-
Hi,
93
-
94
-
Just a heads-up: today, the deprecated [Booking Scraper](https://console.apify.com/actors/5T5NTHWpvetjeRo3i/console) you have been using will be completely unpublished as announced, and you will not be able to use it anymore.
95
-
96
-
If you want to continue to scrape Booking.com, make sure to switch to the [latest Actor version](https://apify.com/voyager/booking-scraper).
97
-
98
-
For any assistance or questions, don't hesitate to reach out to our support team.
90
+
>✉️ **📢 Deprecated Booking Scraper will stop working as announced 📢**
91
+
>
92
+
>Hi,
93
+
>
94
+
>Just a heads-up: today, the deprecated [Booking Scraper](https://console.apify.com/actors/5T5NTHWpvetjeRo3i/console) you have been using will be completely unpublished as announced, and you will not be able to use it anymore.
95
+
>
96
+
>If you want to continue to scrape Booking.com, make sure to switch to the [latest Actor version](https://apify.com/voyager/booking-scraper).
97
+
>
98
+
>For any assistance or questions, don't hesitate to reach out to our support team.
99
99
100
-
101
-
→ remind users to switch to the Actor with a new model.
100
+
Remind users to switch to the Actor with a new model.
102
101
103
102
### 4. After a major issue
104
103
105
104
Actor downtime, performance issues, Actor directly influenced by platform hiccups.
106
105
107
-
✉️ **🛠️ Update on Google Maps Scraper: fixed and ready to go**
108
-
109
-
Hi,
110
-
111
-
We've got a quick update on the Google Maps Scraper for you. If you've been running the Actor this week, you might have noticed some hiccups — scraping was failing for certain places, causing retries and overall slowness.
106
+
>✉️ **🛠️ Update on Google Maps Scraper: fixed and ready to go**
107
+
>
108
+
>Hi,
109
+
>
110
+
>We've got a quick update on the Google Maps Scraper for you. If you've been running the Actor this week, you might have noticed some hiccups — scraping was failing for certain places, causing retries and overall slowness.
111
+
>
112
+
>We apologize for any inconvenience this may have caused you. The **good news is those performance issues are now resolved**. So feel free to resurrect any affected runs using the "latest" build, should work like a charm now.
113
+
>
114
+
>Need a hand or have questions? Feel free to reply to this email.
112
115
113
-
We apologize for any inconvenience this may have caused you. The **good news is those performance issues are now resolved**. So feel free to resurrect any affected runs using the "latest" build, should work like a charm now.
116
+
Apologize to users and or let them know you're working on it/everything is fixed now. This approach helps maintain trust and reassures users that you're addressing the situation.
114
117
115
-
Need a hand or have questions? Feel free to reply to this email.
118
+
:::tip
116
119
117
-
→ apologize to users and or let them know you're working on it/everything is fixed now. This approach helps maintain trust and reassures users that you're addressing the situation.
120
+
It might be an obvious tip, but If you're not great at emails, just write a short draft and ask ChatGPT to polish it. Play with the style until you find the one that suits you. You can even create templates for each situation. If ChatGPT is being too wordy, you can ask it to write at 9th or 10th-grade level, and it will use simpler words and sentences.
118
121
119
-
120
-
💡 It might be an obvious tip, but If you're not great at emails, just write a short draft and ask ChatGPT to polish it. Play with the style until you find the one that suits you. You can even create templates for each situation. If ChatGPT is being too wordy, you can ask it to write at 9th or 10th-grade level, and it will use simpler words and sentences.
122
+
:::
121
123
122
124
## Emails vs. newsletters
123
125
@@ -138,10 +140,8 @@ Here are a few things you can include in your newsletter:
138
140
139
141
Newsletters are a great way to keep your users engaged without overwhelming them. Plus, it's an opportunity to build a more personal connection by showing them you’re actively working to improve the tools they rely on.
140
142
141
-
---
142
-
143
143
## Emailing a separate user
144
144
145
145
There may be times when you need to reach out to a specific user — whether it’s to address a unique situation, ask a question that doesn’t fit the public forum of the **Issue tab**, or explore a collaboration opportunity. While there isn’t a quick way to do this through the Console just yet, you can ensure users can contact you by **adding your email or other contact info to your Store bio**. This makes it easy for them to reach out directly.
146
146
147
-
✍🏻 Learn best practices on how to use your Store bio to connect with your users [Your Store bio]
147
+
✍🏻 Learn best practices on how to use your Store bio to connect with your users [Your Store bio](/academy/get-most-of-actors/interact-with-users/your-store-bio).
The Issues tab is a dedicated section on your Actor’s page where signed-in users can report problems, share feedback, ask questions, and have conversations with you. You can manage each issue thread individually, and the whole thread is visible to everyone. The tab is divided into three categories: **Open**, **Closed**, and **All**, and it shows how long each response has been there. While only signed-in users can post and reply, all visitors can see the interactions, giving your page a transparent and welcoming vibe.
16
16
17
-
🕑 Note that on the web, your average 🕑 **Response time** is calculated and shown in your Actor Metrics. The purpose of this metric is to make it easy for potential users to see how active you are and how well-maintained the Actor is.
17
+
:::note
18
+
19
+
🕑 On the web, your average 🕑 **Response time** is calculated and shown in your Actor Metrics. The purpose of this metric is to make it easy for potential users to see how active you are and how well-maintained the Actor is.
20
+
21
+
:::
18
22
19
23
You can view all the issues related to your Actors by going to **Actors** > [**Issues**](https://console.apify.com/actors?tab=issues) in the Apify Console. Users can get automatic updates on their reported issues or subscribe to issues they are interested in, so they stay informed about any responses. When users report an issue, they’re encouraged to share their run, which helps you get the full context and solve the problem more efficiently. Note that shared runs aren’t visible on the public Actor page.
20
24
21
-
## What is the Issues tab for?
25
+
## What is the Issues tab for
22
26
23
27
The tab is essentially just a series of conversations between you and your users. There are existing systems like GitHub for that. So why create a separate system like an Issues tab? Since the Issues tab exists both in private space (Console) and public space (Actor's page on the web), it can fulfill two different sets of purposes.
24
28
@@ -28,14 +32,14 @@ Originally, the Issues tab was only available in the Apify Console, and its main
28
32
29
33
- Convenience: have a single space to hold the communication between you and your users.
30
34
- Unity and efficiency: make sure multiple users don't submit the same issue through multiple channels or multiple times.
31
-
- Transparency**:** make sure users have their issues addressed publicly and professionally. You can’t delete issues, you can only close them, so there's a clear record of what's been resolved and how.
35
+
- Transparency: make sure users have their issues addressed publicly and professionally. You can’t delete issues, you can only close them, so there's a clear record of what's been resolved and how.
32
36
- Quality of service and innovation: make sure the Actor gets fixed and continuously improved, and users get the quality scraping services they pay for.
33
37
34
38
### Issues tab on the web
35
39
36
40
Now that the Issues tab is public and on the web, it also serves other goals:
37
41
38
-
- Credibility: new users can check how active and reliable you are by looking at the issues and your average 🕑 **Response time** even before trying your Actor**.** It also levels their expectations on when to expect a response from you.
42
+
- Credibility: new users can check how active and reliable you are by looking at the issues and your average 🕑 **Response time** even before trying your Actor. It also levels their expectations on when to expect a response from you.
39
43
- Collaboration: developers can learn from each other’s support styles, which motivates everyone to maintain good interactions and keep up good quality work.
40
44
- SEO boost: every issue now generates its own URL, potentially driving more keyword traffic to your Actor's page
41
45
@@ -45,46 +49,47 @@ Check out how the team behind the **Apollo.io leads scraper** manages their [Iss
45
49
46
50
Note that this Actor is a rental, so users expect a high-quality service.
❗ Once your Actor is public, you’re required to have an Issues tab.
56
+
Once your Actor is public, you’re required to have an Issues tab.
51
57
58
+
:::
52
59
53
60
## SEO of the Issues tab
54
61
55
62
Yes, you read that right! The public Issues tab can boost your SEO. Each issue now has its own URL, which means every report could help your Actor rank for relevant keywords.
56
63
57
64
When we made the tab public, we took inspiration from StackOverflow’s SEO strategy. Even though StackOverflow started as a Q&A forum, its strong SEO has been key to its success. Similarly, your Actor’s Issues tab can help bring in more traffic, with each question and answer potentially generating more visibility. This makes it easier for users to find solutions quickly.
58
65
59
-
---
60
-
61
66
## Tips for handling Actor issues
62
67
63
-
1.**Don’t stay silent**
68
+
1._Don’t stay silent_
64
69
65
70
Respond quickly, even if it’s just a short note. Even if an issue takes weeks to resolve, keep the user in the loop. A quick update prevents frustration and shows the user (and others following it) that you’re actively working on solving the issue.
66
71
67
-
2.**Encourage search to avoid duplication**
72
+
2._Encourage search to avoid duplication_
68
73
69
74
Save time by encouraging users to search for existing issues before submitting new ones. If a similar issue exists, they can follow that thread for updates instead of creating a new one.
70
75
71
-
3.**Encourage reporters to be specific**
76
+
3._Encourage reporters to be specific_
72
77
73
78
The more context, the better! Ask users to share details about their run, which helps you diagnose issues faster. If needed, remind them that runs are shared privately, so sensitive data won’t be exposed.
74
79
75
-
4.**Use screenshots and links**
80
+
4._Use screenshots and links_
76
81
77
82
The same goes for your side. Screenshots and links to specific runs make your answers much clearer. It’s easier to walk the user through a solution if they can see what you’re referencing.
78
83
79
-
5.**Structure issue reporting**
84
+
5._Structure issue reporting_
80
85
81
86
As you get more experienced, you’ll notice common types of issues: bugs, feature requests, questions, reports, misc. This way, you can prioritize and respond faster based on the category.
82
87
83
-
6.**Have ready answers for common categories**
88
+
6._Have ready answers for common categories_
84
89
85
90
Once you recognize recurring types of issues, have pre-prepared responses. For example, if it’s a bug report, you might already have a troubleshooting guide you can link to, or if it’s a feature request, you can figure out the development timeline.
86
91
87
-
7.**Be polite and precise**
92
+
7._Be polite and precise_
88
93
89
94
Politeness goes a long way! Make sure your responses are respectful and straight to the point. It helps to keep things professional, even if the issue seems minor.
Copy file name to clipboardExpand all lines: sources/academy/platform/get_most_of_actors/interact_with_users/your_store_bio.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,26 @@ Everything is neatly available under a single URL, which makes it super easy to
23
23
24
24
Need some inspiration? Check out examples of how others are using their Store bio and README. You can set yours up by heading to **Settings > Account > Profile.**
0 commit comments