Loading Profile...
![Jay R. [dlvr.it]](http://s3.amazonaws.com/satisfaction-production/public/uploaded_images/4556126/NewJayAnime_small.png){kind=small}
Source-Side Prefix and Suffix
As far as I can tell, with Dlvr.it, you can only specify prefixes and suffixes to your notices in a "Destination". Assuming I want individual prefixes for each of the sources that publish to that destination, I cannot achieve that. It would be nice if Prefixes and Suffixes were route-specific, and not destination-specific.
For an example of the result, see http://twitter.com/habslive
For an example of the result, see http://twitter.com/habslive
4
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company implemented this idea.
-
Inappropriate?Hi Pier-Luc, Thanks for the feedback! We'll let you know when that's available. In the mean time you could create two (or more) routes that have their own Prefixes and Suffixes and point them all to the same Twitter account as a workaround.
I’m thankful
1 Comment
Add a comment
This is one of the best points
-
I actually tried to do that before, as a workaround, but it wouldn't let me do it because it was an existing destination respectively Twitter account. It seems that your system doesn't let one use the same destination in multiple routes separately.
This was several days ago, so if you didn't change anything since then it should still be the case. :) -
Inappropriate?Simon, can you explain further what you were trying? The system is designed to allow that, and I just tested that it's allowed.
If you create a new Route, and then select Use Existing when choosing your destination, you can change the options used when posting with that account.
You are correct that if you try to do a New setup and reuse a Twitter account that is already defined, an error will be displayed.2 Comments Add a comment
This is one of the best points
-
Hmm, must've been an error on my end then.
Wasn't a big deal for me so I didn't investigate further at the time, still isn't. Would be a useful feature for Twitter accounts with multiple feeds that would like to disclose sources nonetheless. :) -
I see what you mean Jay. I think it's a bit unfriendly though. The top "Add" button for source allows you to setup an existing destination, but the "+add" button in the "source" box doesn't. It's kind of confusing that you group items by sources and not by destination.
-
Inappropriate?Pier-Luc, I'm not quite sure I understand.
A source can be re-added, or cloned, multiple times in a single route because each use of that source may have different settings (e.g. content filters).
Destinations can only be setup once (in a single route), because otherwise everything would be posted multiple times.1 Comment Add a comment
This is one of the best points
-
The instinctive way would be this:
1. Set up a destination
2. Set up a source
3. Add sources for same destination without having to clone a destination, just have destination options (prefix, suffix) source-specific.
My instinct was to add a source to an existing destination, not add a new source and clone a destination. -
Inappropriate?Our UI operates on the base concept of the Route which is the service that connects (one or more of) your Sources to (one or more of) your Destinations.
Source pre/postfix support is on our roadmap and will be available, but you can easily accomplish what you're describing by creating a single Route for each Destination and Source pair, and setting up the pre/postfix on the Destination. -
Inappropriate?We've added prefix/suffix support on the source side. We continue to support prefix/suffix on the destination side as well.
Further, you can use source and destination prefixes/suffixes in a single route. If you were to use all four fields in a single route the output would be:
[Destination Prefix] [Source Prefix] Headline Body URL [Source Suffix] [Destination Suffix]
If used, the destination prefix/suffix will always appear at the very beginning and very end of the output string -- effectively wrapping the rest of the content.
This approach provides a tremendous amount of flexibility and control over prefixes/suffixes. Post away!
I’m enthusiastic!
-
Inappropriate?Nice! Great implementation. Thanks for the swift reaction!
One question though: how will this affect Stats? For example, if I have 5 sources for 1 destination and I name this route "Test" - all the clicks for any of the sources will be aggregated under "Test", correct?
I’m thankful
-
Inappropriate?You are correct. Stats are aggregated at the route level. In your example, the stats for the five sources would be aggregated into the route "Test". You can still drill down into details on individual posts.
1 person thinks
this is one of the best points
EMPLOYEE
![Jay R. [dlvr.it]](http://s3.amazonaws.com/satisfaction-production/public/uploaded_images/4556126/NewJayAnime_medium.png)
EMPLOYEE
EMPLOYEE
